User equipment assisted secondary node configuration and packet data convergence protocol scheduling for multiple connectivity

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment may transmit, to a base station, assistance information that indicates a packet data convergence protocol (PDCP) preference for multiple connectivity communications from a master node and one or more secondary nodes; and receive, from the base station, a communication that indicates a routing of a sequence of PDCP packages across the master node and one or more active secondary nodes. Numerous other aspects are provided.

CROSS-REFERENCE TO RELATED APPLICATION

This Patent Application claims priority to U.S. Provisional PatentApplication No. 62/705,942, filed on July 23, 2020, entitled “USEREQUIPMENT ASSISTED SECONDARY NODE CONFIGURATION AND PACKET DATACONVERGENCE PROTOCOL SCHEDULING FOR MULTIPLE CONNECTIVITY” and assignedto the assignee hereof. The disclosure of the prior Application isconsidered part of and is incorporated by reference into this PatentApplication.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication and to techniques and apparatuses for user equipmentassisted secondary node configuration and packet data convergenceprotocol scheduling for multiple connectivity.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency division multipleaccess (FDMA) systems, orthogonal frequency division multiple access(OFDMA) systems, single-carrier frequency division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless network may include one or more base stations that supportcommunication for a user equipment (UE) or multiple UEs. A UE maycommunicate with a base station via downlink communications and uplinkcommunications. “Downlink” (or “DL”) refers to a communication link fromthe base station to the UE, and “uplink” (or “UL”) refers to acommunication link from the UE to the base station.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent UEs to communicate on a municipal, national, regional, and/orglobal level. NR, which may be referred to as 5G, is a set ofenhancements to the LTE mobile standard promulgated by the 3GPP. NR isdesigned to better support mobile broadband internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingorthogonal frequency division multiplexing (OFDM) with a cyclic prefix(CP) (CP-OFDM) on the downlink, using CP-OFDM and/or single-carrierfrequency division multiplexing (SC-FDM) (also known as discrete Fouriertransform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supportingbeamforming, multiple-input multiple-output (MIMO) antenna technology,and carrier aggregation. As the demand for mobile broadband accesscontinues to increase, further improvements in LTE, NR, and other radioaccess technologies remain useful.

SUMMARY

In some aspects, a method of wireless communication performed by a UEincludes: transmitting, to a base station, assistance information thatindicates a packet data convergence protocol (PDCP) preference formultiple connectivity communications from a master node and one or moresecondary nodes; and receiving, from the base station, a communicationthat indicates a routing of a sequence of PDCP packages across themaster node and one or more active secondary nodes.

In some aspects, a method of wireless communication performed by a UEincludes: transmitting, to a base station, assistance information thatindicates a secondary node configuration preference for multipleconnectivity communications from a master node and one or more secondarynodes; and receiving, from the base station, a communication thatindicates a secondary node configuration for the UE.

In some aspects, a UE for wireless communication includes: a memory andone or more processors coupled to the memory, the one or more processorsconfigured to: transmit, to a base station, assistance information thatindicates a PDCP preference for multiple connectivity communicationsfrom a master node and one or more secondary nodes; and receive, fromthe base station, a communication that indicates a routing of a sequenceof PDCP packages across the master node and one or more active secondarynodes.

In some aspects, a UE for wireless communication includes: a memory andone or more processors coupled to the memory, the one or more processorsconfigured to: transmit, to a base station, assistance information thatindicates a secondary node configuration preference for multipleconnectivity communications from a master node and one or more secondarynodes; and receive, from the base station, a communication thatindicates a secondary node configuration for the UE.

In some aspects, a non-transitory computer-readable medium storing a setof instructions for wireless communication includes: one or moreinstructions that, when executed by one or more processors of a UE,cause the UE to: transmit, to a base station, assistance informationthat indicates a PDCP preference for multiple connectivitycommunications from a master node and one or more secondary nodes; andreceive, from the base station, a communication that indicates a routingof a sequence of PDCP packages across the master node and one or moreactive secondary nodes.

In some aspects, a non-transitory computer-readable medium storing a setof instructions for wireless communication includes: one or moreinstructions that, when executed by one or more processors of a UE,cause the UE to: transmit, to a base station, assistance informationthat indicates a secondary node configuration preference for multipleconnectivity communications from a master node and one or more secondarynodes; and receive, from the base station, a communication thatindicates a secondary node configuration for the UE.

In some aspects, an apparatus for wireless communication includes: meansfor transmitting, to a base station, assistance information thatindicates a PDCP preference for multiple connectivity communicationsfrom a master node and one or more secondary nodes; and means forreceiving, from the base station, a communication that indicates arouting of a sequence of PDCP packages across the master node and one ormore active secondary nodes.

In some aspects, an apparatus for wireless communication includes: meansfor transmitting, to a base station, assistance information thatindicates a secondary node configuration preference for multipleconnectivity communications from a master node and one or more secondarynodes; and means for receiving, from the base station, a communicationthat indicates a secondary node configuration.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, and/or processing system assubstantially described herein with reference to and as illustrated bythe drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages, will be betterunderstood from the following description when considered in connectionwith the accompanying figures. Each of the figures is provided for thepurposes of illustration and description, and not as a definition of thelimits of the claims.

While aspects are described in the present disclosure by illustration tosome examples, those skilled in the art will understand that suchaspects may be implemented in many different arrangements and scenarios.Techniques described herein may be implemented using different platformtypes, devices, systems, shapes, sizes, and/or packaging arrangements.For example, some aspects may be implemented via integrated chipembodiments or other non-module-component based devices (e.g., end-userdevices, vehicles, communication devices, computing devices, industrialequipment, retail/purchasing devices, medical devices, and/or artificialintelligence devices). Aspects may be implemented in chip-levelcomponents, modular components, non-modular components, non-chip-levelcomponents, device-level components, and/or system-level components.Devices incorporating described aspects and features may includeadditional components and features for implementation and practice ofclaimed and described aspects. For example, transmission and receptionof wireless signals may include one or more components for analog anddigital purposes (e.g., hardware components including antennas, radiofrequency (RF) chains, power amplifiers, modulators, buffers,processors, interleavers, adders, and/or summers). It is intended thataspects described herein may be practiced in a wide variety of devices,components, systems, distributed arrangements, and/or end-user devicesof varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network, inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a base station incommunication with a user equipment (UE) in a wireless network, inaccordance with the present disclosure.

FIG. 3 is a diagram illustrating an example of NR dual connectivity, inaccordance with the present disclosure.

FIG. 4 is a diagram illustrating an example of NR multiple connectivity,in accordance with the present disclosure.

FIG. 5 is a diagram illustrating an example associated with UE assistedpacket data convergence protocol (PDCP) scheduling for multipleconnectivity, in accordance with the present disclosure.

FIG. 6 is a diagram illustrating an example associated with UE assistedsecondary node configuration for multiple connectivity, in accordancewith the present disclosure.

FIG. 7 is a diagram illustrating an example associated with UE assistedsecondary node configuration and/or PDCP scheduling for multipleconnectivity, in accordance with the present disclosure

FIGS. 8 and 9 are diagrams illustrating example processes performed, forexample, by a UE, in accordance with the present disclosure.

FIGS. 10 and 11 are diagrams illustrating example processes performed,for example, by a base station, in accordance with the presentdisclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. One skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the disclosure disclosed herein, whether implementedindependently of or combined with any other aspect of the disclosure.For example, an apparatus may be implemented or a method may bepracticed using any number of the aspects set forth herein. In addition,the scope of the disclosure is intended to cover such an apparatus ormethod which is practiced using other structure, functionality, orstructure and functionality in addition to or other than the variousaspects of the disclosure set forth herein. It should be understood thatany aspect of the disclosure disclosed herein may be embodied by one ormore elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

While aspects may be described herein using terminology commonlyassociated with a 5G or New Radio (NR) radio access technology (RAT),aspects of the present disclosure can be applied to other RATs, such asa 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100,in accordance with the present disclosure. The wireless network 100 maybe or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g.,Long Term Evolution (LTE)) network, among other examples. The wirelessnetwork 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110 b, a BS 110 c, and a BS 110 d), a user equipment (UE) 120 ormultiple UEs 120 (shown as a UE 120 a, a UE 120 b, a UE 120 c, a UE 120d, and a UE 120 e), and/or other network entities. A base station 110 isan entity that communicates with UEs 120. A base station 110 (sometimesreferred to as a BS) may include, for example, an NR base station, anLTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G),an access point, and/or a transmission reception point (TRP). Each basestation 110 may provide communication coverage for a particulargeographic area. In the Third Generation Partnership Project (3GPP), theterm “cell” can refer to a coverage area of a base station 110 and/or abase station subsystem serving this coverage area, depending on thecontext in which the term is used.

A base station 110 may provide communication coverage for a macro cell,a pico cell, a femto cell, and/or another type of cell. A macro cell maycover a relatively large geographic area (e.g., several kilometers inradius) and may allow unrestricted access by UEs 120 with servicesubscriptions. A pico cell may cover a relatively small geographic areaand may allow unrestricted access by UEs 120 with service subscription.A femto cell may cover a relatively small geographic area (e.g., a home)and may allow restricted access by UEs 120 having association with thefemto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A basestation 110 for a macro cell may be referred to as a macro base station.A base station 110 for a pico cell may be referred to as a pico basestation. A base station 110 for a femto cell may be referred to as afemto base station or an in-home base station. In the example shown inFIG. 1, the BS 110 a may be a macro base station for a macro cell 102 a,the BS 110 b may be a pico base station for a pico cell 102 b, and theBS 110 c may be a femto base station for a femto cell 102 c. A basestation may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of a basestation 110 that is mobile (e.g., a mobile base station). In someexamples, the base stations 110 may be interconnected to one anotherand/or to one or more other base stations 110 or network nodes (notshown) in the wireless network 100 through various types of backhaulinterfaces, such as a direct physical connection or a virtual network,using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relaystation is an entity that can receive a transmission of data from anupstream station (e.g., a base station 110 or a UE 120) and send atransmission of the data to a downstream station (e.g., a UE 120 or abase station 110). A relay station may be a UE 120 that can relaytransmissions for other UEs 120. In the example shown in FIG. 1, the BS110 d (e.g., a relay base station) may communicate with the BS 110 a(e.g., a macro base station) and the UE 120 d in order to facilitatecommunication between the BS 110 a and the UE 120 d. A base station 110that relays communications may be referred to as a relay station, arelay base station, a relay, or the like.

The wireless network 100 may be a heterogeneous network that includesbase stations 110 of different types, such as macro base stations, picobase stations, femto base stations, relay base stations, or the like.These different types of base stations 110 may have different transmitpower levels, different coverage areas, and/or different impacts oninterference in the wireless network 100. For example, macro basestations may have a high transmit power level (e.g., 5 to 40 watts)whereas pico base stations, femto base stations, and relay base stationsmay have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of basestations 110 and may provide coordination and control for these basestations 110. The network controller 130 may communicate with the basestations 110 via a backhaul communication link. The base stations 110may communicate with one another directly or indirectly via a wirelessor wireline backhaul communication link.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE 120 may be stationary or mobile. A UE 120 may include, forexample, an access terminal, a terminal, a mobile station, and/or asubscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone),a personal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a laptop computer, a cordlessphone, a wireless local loop (WLL) station, a tablet, a camera, a gamingdevice, a netbook, a smartbook, an ultrabook, a medical device, abiometric device, a wearable device (e.g., a smart watch, smartclothing, smart glasses, a smart wristband, smart jewelry (e.g., a smartring or a smart bracelet)), an entertainment device (e.g., a musicdevice, a video device, and/or a satellite radio), a vehicular componentor sensor, a smart meter/sensor, industrial manufacturing equipment, aglobal positioning system device, and/or any other suitable device thatis configured to communicate via a wireless medium.

Some UEs 120 may be considered machine-type communication (MTC) orevolved or enhanced machine-type communication (eMTC) UEs. An MTC UEand/or an eMTC UE may include, for example, a robot, a drone, a remotedevice, a sensor, a meter, a monitor, and/or a location tag, that maycommunicate with a base station, another device (e.g., a remote device),or some other entity. Some UEs 120 may be considered Internet-of-Things(IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT)devices. Some UEs 120 may be considered a Customer Premises Equipment. AUE 120 may be included inside a housing that houses components of the UE120, such as processor components and/or memory components. In someexamples, the processor components and the memory components may becoupled together. For example, the processor components (e.g., one ormore processors) and the memory components (e.g., a memory) may beoperatively coupled, communicatively coupled, electronically coupled,and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in agiven geographic area. Each wireless network 100 may support aparticular RAT and may operate on one or more frequencies. A RAT may bereferred to as a radio technology, an air interface, or the like. Afrequency may be referred to as a carrier, a frequency channel, or thelike. Each frequency may support a single RAT in a given geographic areain order to avoid interference between wireless networks of differentRATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120 a and UE120e) may communicate directly using one or more sidelink channels(e.g., without using a base station 110 as an intermediary tocommunicate with one another). For example, the UEs 120 may communicateusing peer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or amesh network. In such examples, a UE 120 may perform schedulingoperations, resource selection operations, and/or other operationsdescribed elsewhere herein as being performed by the base station 110.

Devices of the wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided by frequency orwavelength into various classes, bands, channels, or the like. Forexample, devices of the wireless network 100 may communicate using oneor more operating bands. In 5G NR, two initial operating bands have beenidentified as frequency range designations FR1 (410 MHz-7.125 GHz) andFR2 (24.25 GHz-52.6 GHz). It should be understood that although aportion of FR1 is greater than 6 GHz, FR1 is often referred to(interchangeably) as a “Sub-6 GHz” band in various documents andarticles. A similar nomenclature issue sometimes occurs with regard toFR2, which is often referred to (interchangeably) as a “millimeter wave”band in documents and articles, despite being different from theextremely high frequency (EHF) band (30 GHz-300 GHz) which is identifiedby the International Telecommunications Union (ITU) as a “millimeterwave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics and/or FR2 characteristics, and thus may effectivelyextend features of FR1 and/or FR2 into mid-band frequencies. Inaddition, higher frequency bands are currently being explored to extend5G NR operation beyond 52.6 GHz. For example, three higher operatingbands have been identified as frequency range designations FR4a or FR4-1(52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise,it should be understood that the term “sub-6 GHz” or the like, if usedherein, may broadly represent frequencies that may be less than 6 GHz,may be within FR1, or may include mid-band frequencies. Further, unlessspecifically stated otherwise, it should be understood that the term“millimeter wave” or the like, if used herein, may broadly representfrequencies that may include mid-band frequencies, may be within FR2,FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It iscontemplated that the frequencies included in these operating bands(e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified,and techniques described herein are applicable to those modifiedfrequency ranges.

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1.

FIG. 2 is a diagram illustrating an example 200 of a base station 110 incommunication with a UE 120 in a wireless network 100, in accordancewith the present disclosure. The base station 110 may be equipped with aset of antennas 234 a through 234 t, such as T antennas (T≥1). The UE120 may be equipped with a set of antennas 252 a through 252 r, such asR antennas (R≥1).

At the base station 110, a transmit processor 220 may receive data, froma data source 212, intended for the UE 120 (or a set of UEs 120). Thetransmit processor 220 may select one or more modulation and codingschemes (MCSs) for the UE 120 based at least in part on one or morechannel quality indicators (CQIs) received from that UE 120. The UE 120may process (e.g., encode and modulate) the data for the UE 120 based atleast in part on the MCS(s) selected for the UE 120 and may provide datasymbols for the UE 120. The transmit processor 220 may process systeminformation (e.g., for semi-static resource partitioning information(SRPI)) and control information (e.g., CQI requests, grants, and/orupper layer signaling) and provide overhead symbols and control symbols.The transmit processor 220 may generate reference symbols for referencesignals (e.g., a cell-specific reference signal (CRS) or a demodulationreference signal (DMRS)) and synchronization signals (e.g., a primarysynchronization signal (PSS) or a secondary synchronization signal(SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor230 may perform spatial processing (e.g., precoding) on the datasymbols, the control symbols, the overhead symbols, and/or the referencesymbols, if applicable, and may provide a set of output symbol streams(e.g., T output symbol streams) to a corresponding set of modems 232(e.g., T modems), shown as modems 232 a through 232 t. For example, eachoutput symbol stream may be provided to a modulator component (shown asMOD) of a modem 232. Each modem 232 may use a respective modulatorcomponent to process a respective output symbol stream (e.g., for OFDM)to obtain an output sample stream. Each modem 232 may further use arespective modulator component to process (e.g., convert to analog,amplify, filter, and/or upconvert) the output sample stream to obtain adownlink signal. The modems 232 a through 232 t may transmit a set ofdownlink signals (e.g., T downlink signals) via a corresponding set ofantennas 234 (e.g., T antennas), shown as antennas 234 a through 234 t.

At the UE 120, a set of antennas 252 (shown as antennas 252 a through252 r) may receive the downlink signals from the base station 110 and/orother base stations 110 and may provide a set of received signals (e.g.,R received signals) to a set of modems 254 (e.g., R modems), shown asmodems 254 a through 254 r. For example, each received signal may beprovided to a demodulator component (shown as DEMOD) of a modem 254.Each modem 254 may use a respective demodulator component to condition(e.g., filter, amplify, downconvert, and/or digitize) a received signalto obtain input samples. Each modem 254 may use a demodulator componentto further process the input samples (e.g., for OFDM) to obtain receivedsymbols. A MIMO detector 256 may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable,and may provide detected symbols. A receive processor 258 may process(e.g., demodulate and decode) the detected symbols, may provide decodeddata for the UE 120 to a data sink 260, and may provide decoded controlinformation and system information to a controller/processor 280. Theterm “controller/processor” may refer to one or more controllers, one ormore processors, or a combination thereof. A channel processor maydetermine a reference signal received power (RSRP) parameter, a receivedsignal strength indicator (RSSI) parameter, a reference signal receivedquality (RSRQ) parameter, and/or a CQI parameter, among other examples.In some examples, one or more components of the UE 120 may be includedin a housing 284.

The network controller 130 may include a communication unit 294, acontroller/processor 290, and a memory 292. The network controller 130may include, for example, one or more devices in a core network. Thenetwork controller 130 may communicate with the base station 110 via thecommunication unit 294.

One or more antennas (e.g., antennas 234 a through 234 t and/or antennas252 a through 252 r) may include, or may be included within, one or moreantenna panels, one or more antenna groups, one or more sets of antennaelements, and/or one or more antenna arrays, among other examples. Anantenna panel, an antenna group, a set of antenna elements, and/or anantenna array may include one or more antenna elements (within a singlehousing or multiple housings), a set of coplanar antenna elements, a setof non-coplanar antenna elements, and/or one or more antenna elementscoupled to one or more transmission and/or reception components, such asone or more components of FIG. 2.

On the uplink, at the UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports that include RSRP, RSSI, RSRQ, and/or CQI) from thecontroller/processor 280. The transmit processor 264 may generatereference symbols for one or more reference signals. The symbols fromthe transmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modems 254 (e.g., for DFT-s-OFDM orCP-OFDM), and transmitted to the base station 110. In some examples, themodem 254 of the UE 120 may include a modulator and a demodulator. Insome examples, the UE 120 includes a transceiver. The transceiver mayinclude any combination of the antenna(s) 252, the modem(s) 254, theMIMO detector 256, the receive processor 258, the transmit processor264, and/or the TX MIMO processor 266. The transceiver may be used by aprocessor (e.g., the controller/processor 280) and the memory 282 toperform aspects of any of the methods described herein (e.g., withreference to FIGS. 5-11).

At the base station 110, the uplink signals from UE 120 and/or other UEsmay be received by the antennas 234, processed by the modem 232 (e.g., ademodulator component, shown as DEMOD, of the modem 232), detected by aMIMO detector 236 if applicable, and further processed by a receiveprocessor 238 to obtain decoded data and control information sent by theUE 120. The receive processor 238 may provide the decoded data to a datasink 239 and provide the decoded control information to thecontroller/processor 240. The base station 110 may include acommunication unit 244 and may communicate with the network controller130 via the communication unit 244. The base station 110 may include ascheduler 246 to schedule one or more UEs 120 for downlink and/or uplinkcommunications. In some examples, the modem 232 of the base station 110may include a modulator and a demodulator. In some examples, the basestation 110 includes a transceiver. The transceiver may include anycombination of the antenna(s) 234, the modem(s) 232, the MIMO detector236, the receive processor 238, the transmit processor 220, and/or theTX MIMO processor 230. The transceiver may be used by a processor (e.g.,the controller/processor 240) and the memory 242 to perform aspects ofany of the methods described herein (e.g., with reference to FIGS.5-11).

The controller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform one or more techniques associated with UE assistedsecondary node configuration and packet data convergence protocol (PDCP)scheduling for multiple connectivity, as described in more detailelsewhere herein. For example, the controller/processor 240 of the basestation 110, the controller/processor 280 of the UE 120, and/or anyother component(s) of FIG. 2 may perform or direct operations of, forexample, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 ofFIG. 10, process 1100 of FIG. 11, and/or other processes as describedherein. The memory 242 and the memory 282 may store data and programcodes for the base station 110 and the UE 120, respectively. In someexamples, the memory 242 and/or the memory 282 may include anon-transitory computer-readable medium storing one or more instructions(e.g., code and/or program code) for wireless communication. Forexample, the one or more instructions, when executed (e.g., directly, orafter compiling, converting, and/or interpreting) by one or moreprocessors of the base station 110 and/or the UE 120, may cause the oneor more processors, the UE 120, and/or the base station 110 to performor direct operations of, for example, process 800 of FIG. 8, process 900of FIG. 9, process 1000 of FIG. 10, process 1100 of FIG. 11, and/orother processes as described herein. In some examples, executinginstructions may include running the instructions, converting theinstructions, compiling the instructions, and/or interpreting theinstructions, among other examples.

In some aspects, UE 120 may include means for transmitting, to a basestation, assistance information that indicates a PDCP preference formultiple connectivity communications from a master node and one or moresecondary nodes; and/or means for receiving, from the base station, acommunication that indicates a routing of a sequence of PDCP packagesacross the master node and one or more active secondary nodes. In someaspects, such means may include one or more components of UE 120described in connection with FIG. 2, such as controller/processor 280,transmit processor 264, TX MIMO processor 266, antenna 252, modem 254,MIMO detector 256, receive processor 258, and/or memory 282.

In some aspects, UE 120 may include means for transmitting, to a basestation, assistance information that indicates a secondary nodeconfiguration preference for multiple connectivity communications from amaster node and one or more secondary nodes; and/or means for receiving,from the base station, a communication that indicates a secondary nodeconfiguration for the UE. In some aspects, such means may include one ormore components of UE 120 described in connection with FIG. 2, such ascontroller/processor 280, transmit processor 264, TX MIMO processor 266,antenna 252, modem 254, MIMO detector 256, receive processor 258, and/ormemory 282.

In some aspects, base station 110 may include means for receiving, froma UE, assistance information that indicates a PDCP preference formultiple connectivity communications from a master node and one or moresecondary nodes; and/or means for transmitting, to the UE, acommunication that indicates a routing of a sequence of PDCP packagesacross the master node and one or more active secondary nodes. In someaspects, such means may include one or more components of base station110 described in connection with FIG. 2, such as antenna 234, modem 232,MIMO detector 236, receive processor 238, controller/processor 240,transmit processor 220, TX MIMO processor 230, and/or memory 242.

In some aspects, base station 110 may include means for receiving, froma UE, assistance information that indicates a secondary nodeconfiguration preference for multiple connectivity communications from amaster node and one or more secondary nodes; and/or means fortransmitting, to the UE, a communication that indicates a secondary nodeconfiguration for the UE. In some aspects, such means may include one ormore components of base station 110 described in connection with FIG. 2,such as antenna 234, modem 232, MIMO detector 236, receive processor238, controller/processor 240, transmit processor 220, TX MIMO processor230, and/or memory 242.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofthe controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2.

FIG. 3 is a diagram illustrating an example 300 of NR dual connectivity,in accordance with the present disclosure.

As shown in FIG. 3, in NR, dual connectivity is a feature in which a UEmay communicate with two base stations in order to increase bandwidthand decrease traffic latency. One base station acts as a master node(MN) and the other base station acts as a secondary node (SN). The MNmay be an eNB (e.g., a 4G base station or LTE base station) or a gNBdistributed unit (DU) (e.g., a 5G base station or NR base station). TheSN may be a gNB DU (e.g., a 5G base station or NR base station). The MNand the SN may communicate (e.g., directly or indirectly) with a 4G/LTEcore network and/or a 5G/NR core network (e.g., via a gNB control unit(CU)).

In some cases, dual connectivity may be used together with carrieraggregation. Carrier aggregation is a technology that enables two ormore component carriers (sometimes referred to as carriers) to becombined (e.g., into a single channel) for a single UE to enhance datacapacity. Carriers can be combined in the same or different frequencybands. Additionally, or alternatively, contiguous or non-contiguouscarriers can be combined. In carrier aggregation, a UE may be configuredwith a primary carrier and one or more secondary carriers.

When carrier aggregation is used, there may be a number of serving cells(e.g., one for each carrier). The coverage of the serving cells maydiffer, for example due to different carriers on different frequencybands experiencing different pathloss. A primary serving cell (sometimesreferred to as a primary cell (Pcell)) is served by the primary carrier.One or more secondary serving cells (sometimes referred to as secondarycells (Scells)) are served by the one or more secondary carriers.

In dual connectivity, the MN may communicate with the UE via a mastercell group (MCG). The MCG may include multiple serving cells (e.g., aPcell and one or more Scells) when carrier aggregation is activated. TheMCG may include a single serving cell when carrier aggregation is notactivated. The SN may communicate with the UE via a secondary cell group(SCG). The SCG may include multiple serving cells (e.g., a Pcell and oneor more Scells) when carrier aggregation is activated. The Pcell of anSCG may be referred to as a primary secondary cell (PScell). The SCG mayinclude a single serving cell when carrier aggregation is not activated.In some cases, the MCG may anchor a network connection between the UE120 and the 4G/LTE core network or the 5G/NR core network (e.g., formobility, coverage, and/or control plane information,), and the SCG maybe added as additional carriers to increase throughput (e.g., for datatraffic and/or user plane information).

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3.

FIG. 4 is a diagram illustrating an example 400 of NR multipleconnectivity, in accordance with the present disclosure. In multipleconnectivity, a UE may communicate with two or more base stations inorder to increase bandwidth and decrease traffic latency. Multipleconnectivity may include one or multiple MNs and one or multiple SNs.

As shown in FIG. 4, multiple connectivity may be implemented byextending dual connectivity to include multiple SNs/SCGs. In FIG. 4, DUs405, 410, 415, and 420 may be gNB DUs (e.g., 5G base stations or NR basestations). In the example of FIG. 4, DU 405 is the MN for multipleconnectivity communications with the UE. DU 405 may communicate with theUE via the MCG. Alternatively, the MN may be an eNB (e.g., a 4G basestation or LTE base station). DU 410 is a first SN and DU 415 is asecond SN. The first SN (DU 410), when activated for the UE, maycommunicate with the UE via SCG1. The second SN (DU 420), when activatedfor the UE, may communicate with the UE via SCG2. DU 420 is aneighboring DU. For example, the UE may be outside of a coverage area ofDU 420 provided by SCG3. DU 420 may be used as an SN when the UE movesinto the coverage area of DU 420.

As further shown in FIG. 4, the DUs 405, 410, 415, and 420 may beassociated with the same control unit control plane (CU-CP) and may beassociated with multiple control unit user planes (CU-UPs). The CU-CPmay communicate with the DUs 405, 410, 415, and 420 via an F1-controlfunction (F1-C) interface. The CU-UPs may communicate with the DUs 405,410, 415, and 420 via an F1-use function (F1-U) interface. The CU-CP andthe CU-UPs may communicate via an E1 interface. An Xn interface may beused for communications between multiple gNB control units. The gNBcontrol unit may communicate with the 5G core network. The CU-CP maycommunicate with an access and mobility management function (AMF) of the5G core network via an N2 interface. The CU-UPs may communicate with auser plane function (UPF) of the 5G core network via an N3 interface.

As shown in FIG. 4, multiple SNs (DU 410 and DU 415) may be configuredfor the UE. In order to manage multiple connectivity communications, anSN (e.g., DU 410 and/or DU 415) may be activated or deactivated quicklyusing downlink control information (DCI), medium access control (MAC)control element (MAC-CE), and/or radio resource control (RRC) signaling.When one SN (e.g., DU 410) is activated, other SNs (e.g., DU 415) may beswitched to a dormant/suspended state for power saving purposes. For anSN in a dormant/suspended state (e.g., SN 415), there is no active datatransmission between the SN and the UE, and the UE does not performphysical downlink control channel (PDCCH) monitoring. For candidate SNsconfigured for the UE (e.g., DU 410 and DU 415), relaxed radio resourcemanagement (RRM) is performed by the UE for PScells of the candidateSNs. Resource link monitoring (RLM) (e.g., PDCCH monitoring) isperformed by the UE for the PScell of the activated SN (e.g., DU 410).

As described above, multiple connectivity may utilize a single SN ormultiple SNs. In order to manage multiple connectivity using a single SNor multiple SNs, SN configuration and SN switching are performedcompletely by a base station (or multiple base stations) withoutconsidering UE preferences and/or UE information relating to UE buffersize, mobility, radio frequency variation, quality of service (QoS)parameters, and/or battery consumption. This may result in decreasedthroughput and/or increased latency. For example, in a case where the MNis allocated a PDCP sequence to be transmitted to the UE, the MNforwards different portions of the PDCP sequence to multiple SNs fortransmission to the UE. Multiple SN schedulers independently scheduletransmission of portions (e.g., data blocks) of the PDCP sequence. Theindependent scheduling and transmission of portions of the PDCP sequenceby multiple SNs leads to out of order delivery of the PDCP sequence,resulting in large gaps between portions of the PDCP sequence deliveredin parallel by the SNs. This causes long latency for the UE waiting toperform PDCP reordering, which leads to increased latency and decreasedthroughput of network traffic. In addition, large PDCP sequence gaps maycause the UE to use a larger buffer for PDCP reordering.

Some techniques and apparatuses described herein enable a UE totransmit, to a base station, assistance information that includes a PDCPprotocol preference and/or a secondary node configuration preference formultiple connectivity communications from an MN and one or more SNs. Thebase station may utilize the assistance information in configuring theone or more SNs for multiple connectivity communications for the UEand/or scheduling transmission of a PDCP sequence to the UE by the MNand the one or more SNs. As a result, the base station can tailor the SNconfiguration and the PDCP transmission to the preferences of the UE.This may decrease latency, increase throughput, and allow the UE toconserve computing resources (e.g., memory resources and/or processingresources) associated with the buffer for PDCP recording.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 4.

FIG. 5 is a diagram illustrating an example 500 associated with UEassisted PDCP scheduling for multiple connectivity, in accordance withthe present disclosure. As shown in FIG. 5, example 500 includescommunication between a UE 120, a first base station 110-1, and a secondbase station 110-2. The base stations 110 and the UE 120 may be includedin a wireless network, such as wireless network 100 illustrated anddescribed above in connection with FIG. 1. The base stations 110 and theUE 120 may communicate on a wireless access link, which may include anuplink and a downlink.

As shown by reference number 505, the UE 120 may transmit, to the firstbase station 110-1, assistance information that indicates a PDCPpreference for multiple connectivity communications with an MN and oneor more SNs. In some aspects, the first base station 110-1 may be the MNand the second base station may be an SN. In some aspects, the firstbase station 110-1 may be an SN and second base station 110-2 may be theMN. The assistance information may be transmitted from the UE 120 to thefirst base station 110-1 in an RRC communication, an uplink MAC-CE, achannel status information (CSI) report, and/or a combination thereof.

In some aspects, the UE 120 may transmit the assistance information tothe first base station 110-1 during a call setup, call resume, and/orcall handover. For example, the UE 120 may transmit the assistanceinformation in at least one of an RRC setup request, an RRC resumerequest, or a measurement report for a handover.

In some aspects, the UE 120 may transmit the assistance information tothe first base station 110-1 during an ongoing call. For example, the UE120 may transmit the assistance information in at least one of an uplinkMAC-CE, a CSI report, or an RRC communication during an ongoing call.

The assistance information may include the PDCP preference and/or otherUE-specific preferences relating to multiple connectivity for the UE120. In some aspects, the PDCP preference, and/or other UE-specificpreferences may be based at least in part on a buffer size of the UE120, radio frequency variation of the UE 120, QoS parameters for trafficassociated with the UE 120, power/battery consumption of the UE 120,mobility of the UE 120, or a combination thereof.

In some aspects, the PDCP preference indicated in the assistanceinformation may include a PDCP sequence gap preference for the UE 120. APDCP sequence includes multiple data blocks (PDCP packages) that areassigned respective sequence numbers. As used herein, a “portion” of aPDCP sequence refers to one or more data blocks (PDCP packages) of thePDCP sequence. A PDCP sequence gap is a gap between the sequence numbersof portions (e.g., PDCP packages) of the PDCP sequence delivered to theUE 120 in parallel (e.g., in a same time slot) from the MN and theSN(s). The PDCP sequence gap preference may be a preference relating toa size of the PDCP sequence gap for portions of a PDCP sequencetransmitted to the UE 120 by the MN and the SN(s). In some aspects, thePDCP sequence gap preference may specify a maximum PDCP sequence gapand/or a minimum PDCP sequence gap for the UE 120. The PDCP sequence gappreference may be based at least in part on the buffer size of the UE120, latency parameters of traffic associated with the UE 120, and/or acombination thereof.

In some aspects, the PDCP preference indicated in the assistanceinformation may include a PDCP arrival time preference for the UE 120.The PDCP arrival time preference may be a preference relating to arrivaltimes for portions of a PDCP sequence transmitted to the UE 120 by theMN and the SN(s). In some aspects, the PDCP arrival time preference mayspecify a maximum time difference between arrivals, at the UE 120, ofconsecutive portions of the PDCP sequence from the MN and the SN(S). ThePDCP arrival time preference may be based at least in part on the buffersize of the UE 120, latency parameters of traffic associated with the UE120, and/or a combination thereof.

In some aspects, the PDCP preference indicated in the assistanceinformation may include a PDCP splitting preference and/or a PDCProuting preference. The PDCP splitting preference indicates a preferenceas to whether the MN or one of the active SNs performs splitting of thePDCP packages of the PDCP sequence. The PDCP routing preferenceindicates a preference as to whether the MN or one of the active SNsperforms routing of the PDCP packages of the PDCP sequence.

As further shown in FIG. 5, and by reference number 510, the first basestation 110-1 may transmit the assistance information to the second basestation 110-2. In some aspects, the first base station 110-1 may be theMN and the second base station 110-2 may be an SN. In this case, thefirst base station 110-1 (MN) may transmit the assistance informationreceived from the UE 120 to the second base station 110-2 and/or one ormore other SN base stations.

In some aspects, the first base station 110-1 may be an SN and thesecond base station 110-2 may be the MN. In this case, the first basestation 110-1 (SN) may transmit the assistance information received fromthe UE 120 to the second base station 110-2 (MN). The second basestation 110-2 (MN) may then transmit the assistance information to oneor more other SN base stations. Additionally, and/or alternatively, thefirst base station 110-1 (SN) may send the assistance information to thesecond base station 110-2 (MN) and one or more other SN base stations.

As further shown in FIG. 5, and by reference number 515, the first basestation 110-1 and/or the second base station 110-2 may coordinate PDCPscheduling for the UE 120 based at least in part on the assistanceinformation.

In some aspects, the MN (e.g., the first base station 110-1 or thesecond base station 110-2) and one or more SNs (e.g., the first basestation 110-1 or the second base station 110-2, and/or one or more otherbase stations) may coordinate routing and/or scheduling of a PDCPsequence based at least in part on the assistance information. The MNmay coordinate with the SN(s) to determine routing of the PDCP sequenceacross the MN and the SN(s) to the UE 120 based at least in part on thePDCP preference and/or the SN configuration preference included in theassistance information. For example, the MN may coordinate with theSN(s) to determine which portions of the PDCP sequence will betransmitted by the MN and the SN(s) based at least in part on the PDCPpreference and/or the SN configuration preference included in theassistance information.

In some aspects, the MN may coordinate with the SN(s) to scheduletransmission of the portions of the PDCP sequence by the MN and theSN(s) based at least in part on the PDCP preference. For example, the MNand the SN(s) may communicate scheduling information (e.g., via the Xninterface) and coordinate scheduling transmission of the portions of thePDCP sequence by the MN and SN(s) based at least in part on thescheduling information, the PDCP sequence gap preference, and/or thePDCP arrival time preference. The MN and/or SN(s) may adjust scheduledtransmissions of one or more portions of the PDCP sequence to satisfythe PDCP sequence gap preference and/or the PDCP arrival timepreference. For example, an offset may be added to delay transmission ofa portion of the PDCP sequence by the MN or an SN to satisfy the PDCPsequence gap preference and/or the PDCP arrival time preference. In someaspects, the PDCP sequence gap preference and/or the PDCP arrival timepreference may be included as an input for multiple connectivityscheduling by the MN and/or the SN(s).

As further shown in FIG. 5, and by reference number 520, the first basestation 110-1 may transmit, to the UE 120, a communication indicatingPDCP routing for the UE 120. For example, the communication may be anRRC communication, PDCCH DCI, a downlink MAC-CE, and/or a combinationthereof.

In some aspects, the first base station 110-1 may transmit thecommunication to the UE 120 during a call setup, call resume, orhandover. For example, the communication may be an RRC configurationand/or an RRC reconfiguration based at least in part on an RRC setuprequest, RRC resume request, and/or measurement report received from theUE 120.

In some aspects, the first base station 110-1 may transmit thecommunication during an ongoing call. For example, the communication maybe at least one of a PDCCH DCI, a downlink MAC-CE, or an RRCreconfiguration transmitted from the first base station 110-1 to the UE120 during an ongoing call.

The communication may include an indication of the routing of a PDCPsequence across the MN and the SN(s) based at least in part on theassistance information. In some aspects, the communication may includean indication relating to scheduling transmission, to the UE 120, of theportions of the PDCP sequence from the MN and SN(s) based at least inpart on the PDCP sequence gap preference and/or the PDCP arrival timepreference. In some aspects, the communication may include at least oneportion of the PDCP sequence scheduled based at least in part on thePDCP sequence gap preference and/or the PDCP arrival time preference.

As further shown in FIG. 5, and by reference number 525, the UE 120 mayreceive portions of a PDCP sequence from the first base station 110-1(e.g., MN or SN), the second base station 110-2 (e.g., SN or MN), and/orone or more other SN base stations. As described above, the routing ofthe PDCP sequence across the MN and SN(s) and the scheduling oftransmissions of the portions of the PDCP sequence by the MN and SN(s)may be determined based at least in part on the assistance information.The UE 120 may receive portions of the PDCP sequence transmitted on theMCG associated with the MN and the SCG(s) associated with the activated(non-dormant) SN(s).

As described above, the UE 120 may transmit, to the base station 110,assistance information that indicates a PDCP preference for multipleconnectivity with an MN and one or more SNs. The first base station110-1 (e.g., MN or SN) may coordinate with the second base station 110-2(e.g., SN or MN) to determine PDCP routing and scheduling for the UE 120based at least in part on the assistance information. As a result, thePDCP routing/scheduling can be tailored to the preferences of the UE120, which may increase throughput, decrease latency, and increase powerconservation by the UE 120.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 5.

FIG. 6 is a diagram illustrating an example 600 associated with UEassisted SN configuration for multiple connectivity, in accordance withthe present disclosure. As shown in FIG. 6, example 600 includescommunication between a UE 120, a first base station 110-1, and a secondbase station 110-2. The base stations 110 and the UE 120 may be includedin a wireless network, such as wireless network 100 illustrated anddescribed above in connection with FIG. 1. The base stations 110 and theUE 120 may communicate on a wireless access link, which may include anuplink and a downlink.

As shown by reference number 605, the UE 120 may transmit, to the firstbase station 110-1, assistance information that indicates an SNconfiguration preference for multiple connectivity communications withan MN and one or more SNs. In some aspects, the first base station 110-1may be the MN and the second base station may be an SN. In some aspects,the first base station 110-1 may be an SN and second base station 110-2may be the MN. The assistance information may be transmitted from the UE120 to the first base station 110-1 in an RRC communication, an uplinkMAC-CE, a CSI report, and/or a combination thereof.

In some aspects, the UE 120 may transmit the assistance information tothe first base station 110-1 during a call setup, call resume, and/orcall handover. For example, the UE 120 may transmit the assistanceinformation in at least one of an RRC setup request, an RRC resumerequest, or a measurement report for a handover.

In some aspects, the UE 120 may transmit the assistance information tothe first base station 110-1 during an ongoing call. For example, the UE120 may transmit the assistance information in at least one of an uplinkMAC-CE, a CSI report, or an RRC communication during an ongoing call.

The assistance information may include the SN configuration preferenceand/or other UE-specific preferences relating to multiple connectivityfor the UE 120. In some aspects, the SN configuration preference and/orother UE-specific preferences may be based at least in part on a buffersize of the UE 120, radio frequency variation of the UE 120, QoSparameters for traffic associated with the UE 120, power/batteryconsumption of the UE 120, mobility of the UE 120, or a combinationthereof.

In some aspects, the SN configuration preference indicated in theassistance information may include a preferred number of activated SNsand/or a preferred number of deactivated SNs for the UE 120. Forexample, the UE 120 may specify a lower number of activated SNs toconserve battery power or may specify a higher number of activated SNsto satisfy QoS parameters for traffic associated with the UE 120.

In some aspects, the SN configuration preference may include apreference regarding which SNs are to be activated and/or which SNs areto be deactivated. For example, the SN configuration preference mayspecify a preferred set of activated SNs and a preferred set ofdeactivated SNs.

In some aspects, the SN configuration preference may include apreference regarding whether to activate SNs in a non-dormant state or adormant state. For example, the SN configuration preference may specifya preferred set of non-dormant activated SNs and a preferred set ofdormant activated SNs.

In some aspects, the SN configuration preference may include one or moreUE feedback preferences for the one or more SNs. The SN configurationpreference may include a UE feedback preference that indicates apreference for the UE 120 to send layer 1 (L1) feedback (e.g., hybridautomatic repeat request (HARD) acknowledgement (ACK)/negativeacknowledgment (NACK) feedback), or layer 2 (L2) feedback (e.g., radiolink control (RLC)/PDCP status) for a communication received from an SN.Additionally, and/or alternatively, the SN configuration preference mayinclude a UE feedback preference that indicates a preference for the UE120 to send feedback (e.g., L1 feedback and/or L2 feedback), for acommunication received from an SN, to that SN, or to the MN. The one ormore UE feedback preferences may be specified as global preferences ofthe UE 120 for multiple SNs, as SN-specific preferences of the UE 120for individual SNs, and/or a combination thereof.

As further shown in FIG. 6, and by reference number 610, the first basestation 110-1 may transmit the assistance information to the second basestation 110-2. In some aspects, the first base station 110-1 may be theMN and the second base station 110-2 may be an SN. In this case, thefirst base station 110-1 (MN) may transmit the assistance informationreceived from the UE 120 to the second base station 110-2 and/or one ormore other SN base stations.

In some aspects, the first base station 110-1 may be an SN and thesecond base station 110-2 may be the MN. In this case, the first basestation 110-1 (SN) may transmit the assistance information received fromthe UE 120 to the second base station 110-2 (MN). The second basestation 110-2 (MN) may then transmit the assistance information to oneor more other SN base stations. Additionally, and/or alternatively, thefirst base station 110-1 (SN) may send the assistance information to thesecond base station 110-2 (MN) and one or more other SN base stations.

As further shown in FIG. 6, and by reference number 615, the first basestation 110-1 and/or the second base station 110-2 may coordinate SNconfiguration for the UE 120 based at least in part on the assistanceinformation.

In some aspects, the first base station 110-1 (e.g., MN or SN) and/orthe second base station 110-2 (e.g., SN or MN) may determine an SNconfiguration or reconfiguration for the UE 120 based at least in parton the SN configuration preference included in the assistanceinformation. For example, the first base station 110-1 (e.g., MN or SN)and/or the second base station 110-2 (e.g., SN or MN) may configureand/or modify the number of activated SNs and deactivated SNs for the UE120, select which SNs are activated and which SNs are deactivated forthe UE 120, and select which of the activated SNs are non-dormant andwhich of the activated SNs are dormant based at least in part on the SNconfiguration preference.

The first base station 110-1 (e.g., MN or SN) and/or the second basestation 110-2 (e.g., SN or MN) may also configure the UE 120 to transmitL1 feedback or L2 feedback based at least in part on the one or more UEfeedback preferences. Additionally, and/or alternatively, the first basestation 110-1 (e.g., MN or SN) and/or the second base station 110-2(e.g., SN or MN) may configure the UE 120 to transmit feedback (e.g., L1feedback and/or L2 feedback), for a communication from an SN, to the SNor to the MN, based at least in part on the one or more UE feedbackpreferences. The first base station 110-1 (e.g., MN or SN) and/or thesecond base station 110-2 (e.g., SN or MN) may also modify the UEfeedback settings based at least in part on the one or more UE feedbackpreferences.

As further shown in FIG. 6, and by reference number 620, the first basestation 110-1 may transmit, to the UE 120, a communication indicatingthe SN configuration for the UE 120. For example, the communication maybe an RRC communication, PDCCH DCI, a downlink MAC-CE, and/or acombination thereof.

In some aspects, the first base station 110-1 may transmit thecommunication to the UE 120 during a call setup, call resume, orhandover. For example, the communication may be an RRC configurationand/or an RRC reconfiguration based at least in part on an RRC setuprequest, RRC resume request, and/or measurement report received from theUE 120. In some aspects, an RRC configuration/reconfiguration,transmitted from the first base station 110-1 to the UE 120, includes anSN configuration/reconfiguration based at least in part on theassistance information received from the UE 120. For example, the SNconfiguration/reconfiguration may indicate the number of activated SNsand deactivated SNs, indicate which SNs are activated and which SNs aredeactivated, indicate which of the activated SNs are non-dormant andwhich of the activated SNs are dormant, and/or indicate one or more UEfeedback settings for the UE 120.

In some aspects, the first base station 110-1 may transmit thecommunication during an ongoing call. For example, the communication maybe at least one of a PDCCH DCI, a downlink MAC-CE, or an RRCreconfiguration transmitted from the first base station 110-1 to the UE120 during an ongoing call. In some aspects, the communication mayinclude an indication of a state change for at least one SN based atleast in part on the SN configuration preference indicated in theassistance information. In some aspects, the communication may includean indication of a change to a UE feedback setting for the UE 120 basedat least in part on the UE feedback preference included in theassistance information.

As further shown in FIG. 6, and by reference number 625, the UE 120 mayreceive portions of a PDCP sequence from the first base station 110-1(e.g., MN or SN), the second base station 110-2 (e.g., SN or MN), and/orone or more other SN base stations. The UE 120 may receive portions ofthe PDCP sequence transmitted on the MCG associated with the MN and theSCG(s) associated with the activated (non-dormant) SN(s). Theconfiguration of the activate SN(s) used to transmit portions of thePDCP sequence to the UE 120 may be determined based at least in part onthe assistance information.

As described above, the UE 120 may transmit, to the base station 110,assistance information that indicates an SN configuration preference formultiple connectivity with an MN and one or more SNs. The first basestation 110-1 (e.g., MN or SN) may coordinate with the second basestation 110-2 (e.g., SN or MN) to determine an SN configuration for theUE 120 based at least in part on the assistance information. As aresult, the SN configuration can be tailored to the preferences of theUE 120, which may increase throughput, decrease latency, and increasepower conservation by the UE 120.

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 6.

FIG. 7 is a diagram illustrating an example 700 associated with UEassisted SN configuration and/or PDCP scheduling for multipleconnectivity, in accordance with the present disclosure. As shown inFIG. 7, example 700 includes communication between a UE 120, a firstbase station 110-1, and a second base station 110-2. The base stations110 and the UE 120 may be included in a wireless network, such aswireless network 100 illustrated and described above in connection withFIG. 1. The base stations 110 and the UE 120 may communicate on awireless access link, which may include an uplink and a downlink.

As shown by reference number 705, during a call setup, a call resume, ora handover, the UE 120 may transmit, to the first base station 110-1,assistance information that indicates a PDCP preference and/or an SNconfiguration preference. For example, the assistance information may beincluded in an RRC setup request, an RRC resume request, or ameasurement report (e.g., CSI report) for a call handover. Additionally,and/or alternatively, the assistance information may be included in anuplink MAC-CE transmitted during the call setup, call resume, orhandover. The assistance information may include the PDCP preference,the SN configuration preference, and/or other UE-specific preferencesrelating to multiple connectivity for the UE 120, as described above inconnection with FIG. 5.

As further shown in FIG. 7, and by reference number 710, the first basestation 110-1 and/or the second base station 110-2 may determine an SNconfiguration for the UE 120 based at least in part on the SNconfiguration preference included in the assistance information. In someaspects, the first base station 110-1 may be the MN and the second basestation 110-2 may be an SN.

In some aspects, the first base station 110-1 may be an SN and secondbase station 110-2 may be the MN. In some aspects, the first basestation 110-1 may determine the SN configuration for the UE 120 based atleast in part on the assistance information. In some aspects, the firstbase station 110-1 may transmit the assistance information to the basestation, and second base station 110-2 may determine the SNconfiguration for the UE 120 based at least in part on the assistanceinformation. In some aspects, the first base station 110-1 maycoordinate with the second base station 110-2 to determine theassistance information.

The first base station 110-1 and/or the second base station 110-2 maydetermine a configuration of the number of activated SNs and the numberof deactivated SNs for the UE 120 based at least in part on the SNconfiguration preference. The first base station 110-1 and/or the secondbase station 110-2 may determine a configuration of which SNs areactivated and which SNs are deactivated for the UE 120 based at least inpart on the SN configuration preference. The first base station 110-1(and/or the second base station 110-2 may determine a configuration ofwhich of the activated SNs are non-dormant and which of the activatedSNs are dormant based at least in part on the SN configurationpreference.

The first base station 110-1 and/or the second base station 110-2 maydetermine a configuration of a feedback mode for the UE 120 based on theone or more UE 120 feedback preferences included in the SN configurationpreference. The first base station 110-1 and/or the second base station110-2 may configure the UE 120 to transmit L1 feedback or L2 feedbackbased at least in part on the one or more UE feedback preferences.Additionally, and/or alternatively, first base station 110-1 and/or thesecond base station 110-2 may configure the UE 120 to transmit feedback(e.g., L1 feedback and/or L2 feedback) for a communication from an SN tothe SN or to the MN, based at least in part on the one or more UEfeedback preferences.

As further shown in FIG. 7, and by reference number 715, the first basestation 110-1 may transmit, to the UE 120, an RRC configuration or RRCreconfiguration that includes the SN configuration for the UE 120. TheSN configuration may indicate the number of activated SNs anddeactivated SNs. The SN configuration may indicate which SNs areactivated and which SNs are deactivated. The SN configuration mayindicate which of the activated SNs are non-dormant and which of theactivated SNs are dormant. The SN configuration may indicate an L1feedback mode or an L2 feedback mode for the UE 120. The SNconfiguration may indicate whether feedback from the UE 120, for acommunication from an SN, is to be transmitted to the SN or to the MN.

As further shown in FIG. 7, and by reference number 720, during anongoing call, the UE 120 may transmit, to the first base station 110-1,assistance information that indicates a PDCP preference and/or an SNconfiguration preference. The assistance information may include thePDCP preference, the SN configuration preference, and/or otherUE-specific preferences relating to multiple connectivity for the UE120, as described above in connection with FIG. 5. In some aspects, thePDCP preference and/or the SN configuration preference included in theassistance information transmitted during the ongoing call may be basedat least in part on the buffer size of the UE 120, the radio frequencyvariation of the UE 120, the QoS parameters for traffic associated withthe UE 120, the power/battery consumption of the UE 120, the mobility ofthe UE 120, or a combination thereof.

As further shown in FIG. 7, and by reference number 725, the first basestation 110-1 and/or the second base station 110-2 may coordinate PDCPscheduling and/or determine an adjustment to the SN configuration basedat least in part on the PDCP preference and/or the SN configurationpreference indicated in the assistance information.

In some aspects, the MN (e.g., the first base station 110-1 or thesecond base station 110-2) and SN(s) (e.g., the first base station 110-1or the second base station 110-2, and/or one or more other basestations) may coordinate routing and/or scheduling of a PDCP sequencebased at least in part on the PDCP preference and/or the SNconfiguration preference. The MN may coordinate with the SN(s) todetermine routing of the PDCP sequence across the MN and the SN(s) tothe UE 120 based at least in part on the PDCP preference and/or the SNconfiguration preference. For example, the MN may coordinate with theSN(s) to determine which portions of the PDCP sequence will betransmitted by the MN and the SN(s) based at least in part on the PDCPpreference and/or the SN configuration preference. In some aspects, theMN or the SN may determine splitting and/or routing of the PDCP packagesbased at least in part on the PDCP splitting preference and/or the PDCProuting preference.

In some aspects, the MN may coordinate with the SN(s) to scheduletransmission of the portions of the PDCP sequence by the MN and theSN(s) based at least in part on the PDCP preference. For example, the MNand the SN(s) may coordinate to schedule transmission of the portions ofthe PDCP sequence by the MN and SN(s) based at least in part on the PDCPsequence gap preference and/or the PDCP arrival time preference. The MNand/or SN(s) may adjust scheduled transmissions of one or more portionsof the PDCP sequence to satisfy the PDCP sequence gap preference and/orthe PDCP arrival time preference. For example, an offset may be added todelay transmission of a portion of the PDCP sequence by the MN or an SNto satisfy the PDCP sequence gap preference and/or the PDCP arrival timepreference. In some aspects, the PDCP sequence gap preference and/or thePDCP arrival time preference may be included as an input for multipleconnectivity scheduling by the MN and/or the SN(s).

In some aspects, the first base station 110-1 and/or the second basestation 110-2 may determine an adjustment to one or more settings in theSN configuration based at least in part on the SN configurationpreference transmitted by the UE 120 during the on-going call. Forexample, the first base station 110-1 and/or the second base station110-2 may determine an adjustment to the number of activated SNs and/orthe number of deactivated SNs for the UE 120, an adjustment to which SNsare activated and which SNs are deactivated, and/or an adjustment towhich of the activated SNs are non-dormant and which of the activatedSNs are dormant, based at least in part on the SN configurationpreference. Additionally, and/or alternatively, the first base station110-1 and/or the second base station 110-2 may determine an adjustmentto a UE feedback setting based at least in part on the SN configurationpreference.

As further shown in FIG. 7, and by reference number 730, the first basestation 110-1 may transmit, to the UE 120, a communication relating tothe PDCP scheduling and/or the adjustment to the SN configuration. Forexample, the communication may be at least one of PDCCH DCI, a downlinkMAC-CE, or an RRC reconfiguration.

The communication may include an indication relating to PDCP schedulingfor the UE 120. In some aspects, the communication may provide anindication of the routing of the PDCP sequence across the MN and theSN(s). In some aspects, the communication may include an indicationrelating to scheduling transmission, to the UE 120, of one or moreportions of the PDCP sequence from the MN and SN(s) based at least inpart on the PDCP sequence gap preference and/or the PDCP arrival timepreference. For example, the communication may be a PDCCH communicationthat includes DCI for scheduling transmission of one or more portions ofthe PDCP from the MN or an SN. In some aspects, the communication mayinclude at least one portion of the PDCP sequence scheduled based atleast in part on the PDCP sequence gap preference and/or the PDCParrival time preference.

In some aspects, the communication may include an indication of anadjustment to the SN configuration. For example, the communication mayinclude an indication of a state change for at least one SN based atleast in part on the SN configuration preference included in theassistance information transmitted by the UE 120 during the on-goingcall. Additionally, and/or alternatively, the communication may includean indication of a change to a UE feedback setting for the UE 120 basedat least in part on the UE feedback preference included in theassistance information transmitted by the UE 120 during the on-goingcall.

As indicated above, FIG. 7 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 7.

FIG. 8 is a diagram illustrating an example process 800 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 800 is an example where the UE (e.g., UE 120) performsoperations associated with UE assisted PDCP scheduling for multipleconnectivity.

As shown in FIG. 8, in some aspects, process 800 may includetransmitting, to a base station, assistance information that indicates aPDCP preference for multiple connectivity communications from a masternode and one or more secondary nodes (block 810). For example, the UE(e.g., using antenna 252, transmit processor 264, TX MIMO processor 266,modem 254, controller/processor 280, and/or memory 282) may transmit, toa base station, assistance information that indicates a PDCP preferencefor multiple connectivity communications from a master node and one ormore secondary nodes, as described above.

As further shown in FIG. 8, in some aspects, process 800 may includereceiving, from the base station, a communication that indicates arouting of a sequence of PDCP packages across the master node and one ormore active secondary nodes (block 820). For example, the UE (e.g.,using antenna 252, modem 254, MIMO detector 256, receive processor 258,controller/processor 280, and/or memory 282) may receive, from the basestation, a communication that indicates a sequence of PDCP packagesacross the master node and one or more active secondary nodes, asdescribed above.

Process 800 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the base station is at least one of the master nodeor a secondary node of the one or more secondary nodes.

In a second aspect, alone or in combination with the first aspect, thePDCP preference includes a preference for a PDCP sequence gap for thePDCP packages transmitted by the master node and the one or more activesecondary nodes.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the preference for the PDCP sequence gap includes atleast one of a minimum PDCP sequence gap or a maximum PDCP sequence gap.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the preference for the PDCP sequence gap isbased at least in part on a buffer size of the UE or latency parametersfor traffic associated with the UE.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the PDCP preference includes a PDCP arrival timepreference for the PDCP packages transmitted by the master node and theone or more active secondary nodes.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the PDCP arrival time preference indicates apreferred maximum time difference between arrivals of consecutive PDCPpackages of the sequence of PDCP packages from the master node and theone or more active secondary nodes.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the PDCP arrival time preference is basedat least in part on a buffer size of the UE or latency parameters fortraffic associated with the UE.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the PDCP preference includes at least oneof a PDCP splitting preference that specifies a preference for themaster node or one of the active secondary nodes to perform splitting ofthe sequence of PDCP packages, or a PDCP routing preference thatspecifies a preference for the master node or one of the activesecondary nodes to perform routing of the sequence of PDCP packages.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the assistance information is included in atleast one of a radio resource control communication, a MAC-CE, or achannel status information report.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the communication is at least one of a radioresource control communication, physical downlink control channeldownlink control information, or a MAC-CE.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the assistance information is included inat least one of a call setup request, a call resume request, or ameasurement report for a call handover.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the assistance information istransmitted to the base station during an ongoing call.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the PDCP preference includes at least oneof a PDCP sequence gap preference or a PDCP arrival time preference, andthe communication includes an indication relating to scheduling deliveryof the sequence of PDCP packages based at least in part on the at leastone of the PDCP sequence gap preference or the PDCP arrival timepreference.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the PDCP preference includes at leastone of a PDCP sequence gap preference or a PDCP arrival time preference,and the communication includes at least one PDCP package of a sequenceof PDCP packages scheduled based at least in part on the at least one ofthe PDCP sequence gap preference or the PDCP arrival time preference.

Although FIG. 8 shows example blocks of process 800, in some aspects,process 800 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 8.Additionally, or alternatively, two or more of the blocks of process 800may be performed in parallel.

FIG. 9 is a diagram illustrating an example process 900 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 900 is an example where the UE (e.g., UE 120) performsoperations associated with UE assisted secondary node configuration formultiple connectivity.

As shown in FIG. 9, in some aspects, process 900 may includetransmitting, to a base station, assistance information that indicates asecondary node configuration preference for multiple connectivitycommunications from a master node and one or more secondary nodes (block910). For example, the UE (e.g., using antenna 252, transmit processor264, TX MIMO processor 266, modem 254, controller/processor 280, and/ormemory 282) may transmit, to a base station, assistance information thatindicates a secondary node configuration preference for multipleconnectivity communications from a master node and one or more secondarynodes, as described above.

As further shown in FIG. 9, in some aspects, process 900 may includereceiving, from the base station, a communication that indicates asecondary node configuration for the UE (block 920). For example, the UE(e.g., using antenna 252, modem 254, MIMO detector 256, receiveprocessor 258, controller/processor 280, and/or memory 282) may receive,from the base station, a communication that indicates a secondary nodeconfiguration for the UE, as described above.

Process 900 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the base station is at least one of the master nodeor a secondary node of the one or more secondary nodes.

In a second aspect, alone or in combination with the first aspect, thesecondary node configuration preference includes at least one of apreferred number of activated secondary nodes or a preferred number ofdeactivated secondary nodes.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the secondary node configuration preference includesat least one of a preferred set of activated secondary nodes of the oneor more secondary nodes or a preferred set of deactivated secondarynodes of the one or more secondary nodes.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the secondary node configuration preferenceincludes at least one of a preferred set of non-dormant activatedsecondary nodes of the one or more secondary nodes or a preferred set ofdormant activated secondary nodes of the one or more secondary nodes.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the secondary node configuration preferenceincludes a UE feedback preference for the one or more secondary nodes.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the UE feedback preference indicates a preferencefor layer 1 feedback or layer 2 feedback from the UE for communicationsreceived from the one or more secondary nodes.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the UE feedback preference indicates apreference to send feedback for communications received from the one ormore secondary nodes to the one or more secondary nodes or a preferenceto send feedback for communications received from the one or moresecondary nodes to the master node.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the assistance information is included inat least one of a radio resource control communication, a MAC-CE, or achannel status information report.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the communication is at least one of a radioresource control communication, physical downlink control channeldownlink control information, or a MAC-CE.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the assistance information is included in atleast one of a call setup request, a call resume request, or ameasurement report for a call handover.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the communication includes the secondarynode configuration, and the secondary node configuration specifies atleast one of a configuration of the one or more secondary nodes formultiple connectivity communications or a re-configuration configurationof the one or more secondary nodes for multiple connectivitycommunications.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the assistance information istransmitted to the base station during an ongoing call.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the communication includes an indicationof a state change for at least one secondary node of the one or moresecondary nodes.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the secondary node configurationpreference includes a UE feedback preference, and the communicationincludes an indication of a change to a feedback mode for the UE basedat least in part on the UE feedback preference.

Although FIG. 9 shows example blocks of process 900, in some aspects,process 900 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 9.Additionally, or alternatively, two or more of the blocks of process 900may be performed in parallel.

FIG. 10 is a diagram illustrating an example process 1000 performed, forexample, by a base station, in accordance with the present disclosure.Example process 1000 is an example where the base station (e.g., basestation 110) performs operations associated with UE assisted PDCPscheduling for multiple connectivity.

As shown in FIG. 10, in some aspects, process 1000 may includereceiving, from a UE, assistance information that indicates a PDCPpreference for multiple connectivity communications from a master nodeand one or more secondary nodes (block 1010). For example, the basestation (e.g., using antenna 234, modem 232, MIMO detector 236, receiveprocessor 238, controller/processor 240, and/or memory 242) may receive,from a UE, assistance information that indicates a PDCP preference formultiple connectivity communications from a master node and one or moresecondary nodes, as described above.

As further shown in FIG. 10, in some aspects, process 1000 may includetransmitting, to the UE, a communication that indicates a routing of asequence of PDCP packages across the master node and one or more activesecondary nodes (block 1020). For example, the base station (e.g., usingtransmit processor 220, TX MIMO processor 230, modulator 232, antenna234, controller/processor 240, memory 242, and/or scheduler 246) maytransmit, to the UE, a communication that indicates a routing of asequence of PDCP packages across the master node and one or more activesecondary nodes, as described above.

Process 1000 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, process 1000 includes coordinating scheduling ofmultiple connectivity communications to the UE with one or more otherbase stations based at least in part on the PDCP preference.

In a second aspect, alone or in combination with the first aspect, thePDCP preference includes at least one of a PDCP sequence gap preferenceor a PDCP arrival time preference, and coordinating scheduling ofmultiple connectivity communications to the UE with the one or moreother base stations comprises coordinating scheduling of delivery of thePDCP sequence to the UE with the one or more other base stations basedat least in part on the at least one of the PDCP sequence gap preferenceor the PDCP arrival time preference.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the base station is at least one of the master nodeor a secondary node of the one or more secondary nodes.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the PDCP preference includes a preferencefor a PDCP sequence gap for the PDCP packages transmitted by the masternode and the one or more active secondary nodes.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the preference for the PDCP sequence gapincludes at least one of a minimum PDCP sequence gap or a maximum PDCPsequence gap.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the preference for the PDCP sequence gap is basedat least in part on a buffer size of the UE or latency parameters fortraffic associated with the UE.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the PDCP preference includes a PDCP arrivaltime preference for the PDCP packages transmitted by the master node andthe one or more active secondary nodes.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the PDCP arrival time preferenceindicates a preferred maximum time difference between arrivals ofconsecutive PDCP packages of the sequence of PDCP packages from themaster node and the one or more active secondary nodes.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the PDCP arrival time preference is based atleast in part on a buffer size of the UE or latency parameters fortraffic associated with the UE.

In an tenth aspect, alone or in combination with one or more of thefirst through ninth aspects, the PDCP preference includes at least oneof a PDCP splitting preference that specifies a preference for themaster node or one of the active secondary nodes to perform splitting ofthe sequence of PDCP packages, or a PDCP routing preference thatspecifies a preference for the master node or one of the activesecondary nodes to perform routing of the sequence of PDCP packages.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the assistance information is included inat least one of a radio resource control communication, a medium accesscontrol (MAC) control element, or a channel status information report.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the communication is at least one of aradio resource control communication, physical downlink control channeldownlink control information, or a MAC-CE.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the assistance information is included inat least one of a call setup request, a call resume request, or ameasurement report for a call handover.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the assistance information is receivedby the base station during an ongoing call.

In a fifteenth aspect, alone or in combination with one or more of thefirst through fourteenth aspects, the PDCP preference includes at leastone of a PDCP sequence gap preference or a PDCP arrival time preference,and the communication includes an indication relating to schedulingdelivery of the sequence of PDCP packages based at least in part on theat least one of the PDCP sequence gap preference or the PDCP arrivaltime preference.

In a sixteenth aspect, alone or in combination with one or more of thefirst through fifteenth aspects, the PDCP preference includes at leastone of a PDCP sequence gap preference or a PDCP arrival time preference,and the communication includes at least one PDCP package of the sequenceof PDCP packages scheduled based at least in part on the at least one ofthe PDCP sequence gap preference or the PDCP arrival time preference.

Although FIG. 10 shows example blocks of process 1000, in some aspects,process 1000 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 10.Additionally, or alternatively, two or more of the blocks of process1000 may be performed in parallel.

FIG. 11 is a diagram illustrating an example process 1100 performed, forexample, by a base station, in accordance with the present disclosure.Example process 1100 is an example where the base station (e.g., basestation 110) performs operations associated with UE assisted secondarynode configuration.

As shown in FIG. 11, in some aspects, process 1100 may includereceiving, from a UE, assistance information that indicates a secondarynode configuration preference for multiple connectivity communicationsfrom a master node and one or more secondary nodes (block 1110). Forexample, the base station (e.g., using antenna 234, demodulator 232,MIMO detector 236, receive processor 238, controller/processor 240,and/or memory 242) may receive, from a UE, assistance information thatindicates a secondary node configuration preference for multipleconnectivity communications from a master node and one or more secondarynodes, as described above.

As further shown in FIG. 11, in some aspects, process 1100 may includetransmitting, to the UE, a communication that indicates a secondary nodeconfiguration for the UE (block 1120). For example, the base station(e.g., using transmit processor 220, TX MIMO processor 230, modulator232, antenna 234, controller/processor 240, memory 242, and/or scheduler246) may transmit, to the UE, a communication that indicates a secondarynode configuration for the UE, as described above.

Process 1100 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, process 1100 includes coordinating scheduling ofmultiple connectivity communications to the UE with one or more otherbase stations based at least in part on the secondary node configurationpreference.

In a second aspect, alone or in combination with the first aspect, thebase station is at least one of the master node or a secondary node ofthe one or more secondary nodes.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the secondary node configuration preference includesat least one of a preferred number of activated secondary nodes or apreferred number of deactivated secondary nodes.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the secondary node configuration preferenceincludes at least one of a preferred set of activated secondary nodes ofthe one or more secondary nodes or a preferred set of deactivatedsecondary nodes of the one or more secondary nodes.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the secondary node configuration preferenceincludes at least one of a preferred set of non-dormant activatedsecondary nodes of the one or more secondary nodes or a preferred set ofdormant activated secondary nodes of the one or more secondary nodes.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the secondary node configuration preferenceincludes a UE feedback preference for the one or more secondary nodes.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the UE feedback preference indicates apreference for layer 1 feedback or layer 2 feedback from the UE forcommunications received from the one or more secondary nodes.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the UE feedback preference indicates apreference to send feedback for communications received from the one ormore secondary nodes to the one or more secondary nodes or a preferenceto send feedback for communications received from the one or moresecondary nodes to the master node.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the assistance information is included in atleast one of a radio resource control communication, a MAC-CE, or achannel status information report.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the communication is at least one of a radioresource control communication, physical downlink control channeldownlink control information, or a MAC-CE.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the assistance information is included inat least one of a call setup request, a call resume request, or ameasurement report for a call handover.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the communication includes the secondarynode configuration, and the secondary node configuration specifies atleast one of a configuration of the one or more secondary nodes formultiple connectivity communications or a re-configuration of the one ormore secondary nodes for multiple connectivity communications.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the assistance information is received bythe base station during an ongoing call.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the communication includes anindication of a state change for at least one secondary node of the oneor more secondary nodes.

In a fifteenth aspect, alone or in combination with one or more of thefirst through fourteenth aspects, the secondary node configurationpreference includes a UE feedback preference, and the communicationincludes an indication of a change to a feedback mode for the UE basedat least in part on the UE feedback preference.

Although FIG. 11 shows example blocks of process 1100, in some aspects,process 1100 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 11.Additionally, or alternatively, two or more of the blocks of process1100 may be performed in parallel.

The following provides an overview of some Aspects of the presentdisclosure:

Aspect 1: A method of wireless communication performed by a userequipment (UE), comprising: transmitting, to a base station, assistanceinformation that indicates a packet data convergence protocol (PDCP)preference for multiple connectivity communications from a master nodeand one or more secondary nodes; and receiving, from the base station, acommunication that indicates a routing of a sequence of PDCP packagesacross the master node and one or more active secondary nodes.

Aspect 2: The method of Aspect 1, wherein the base station is at leastone of the master node or a secondary node of the one or more secondarynodes.

Aspect 3: The method of any of Aspects 1-2, wherein the PDCP preferenceincludes a preference for a PDCP sequence gap for the PDCP packagestransmitted by the master node and the one or more active secondarynodes.

Aspect 4: The method of Aspect 3, wherein the preference for the PDCPsequence gap includes at least one of a minimum PDCP sequence gap or amaximum PDCP sequence gap.

Aspect 5: The method of any of Aspects 3-4, wherein the preference forthe PDCP sequence gap is based at least in part on a buffer size of theUE or latency parameters for traffic associated with the UE.

Aspect 6: The method of any of Aspects 1-5, wherein the PDCP preferenceincludes a PDCP arrival time preference for the PDCP packagestransmitted by the master node and the one or more active secondarynodes.

Aspect 7: The method of Aspect 6, wherein the PDCP arrival timepreference indicates a preferred maximum time difference betweenarrivals of consecutive PDCP packages of the sequence of PDCP packagesfrom the master node and the one or more active secondary nodes.

Aspect 8: The method of any of Aspects 6-7, wherein the PDCP arrivaltime preference is based at least in part on a buffer size of the UE orlatency parameters for traffic associated with the UE.

Aspect 9: The method of any of Aspects 1-8, wherein the PDCP preferenceincludes at least one of a PDCP splitting preference that specifies apreference for the master node or one of the active secondary nodes toperform splitting of the sequence of PDCP packages, or a PDCP routingpreference that specifies a preference for the master node or one of theactive secondary nodes to perform routing of the sequence of PDCPpackages.

Aspect 10: The method of any of Aspects 1-9, wherein the assistanceinformation is included in at least one of a radio resource controlcommunication, a medium access control (MAC) control element, or achannel status information report.

Aspect 11: The method of any of Aspects 1-10, wherein the communicationis at least one of a radio resource control communication, physicaldownlink control channel downlink control information, or a mediumaccess control (MAC) control element.

Aspect 12: The method of any of Aspects 1-11, wherein the assistanceinformation is included in at least one of a call setup request, a callresume request, or a measurement report for a call handover.

Aspect 13: The method of any of Aspects 1-12, wherein the assistanceinformation is transmitted to the base station during an ongoing call.

Aspect 14: The method of any of Aspects 13, wherein the PDCP preferenceincludes at least one of a PDCP sequence gap preference or a PDCParrival time preference, and the communication includes an indicationrelating to scheduling delivery of the sequence of PDCP packages basedat least in part on the at least one of the PDCP sequence gap preferenceor the PDCP arrival time preference.

Aspect 15: The method of any of Aspects 13-14, wherein the PDCPpreference includes at least one of a PDCP sequence gap preference or aPDCP arrival time preference, and the communication includes at leastone PDCP package of a sequence of PDCP packages scheduled based at leastin part on the at least one of the PDCP sequence gap preference or thePDCP arrival time preference.

Aspect 16: A method of wireless communication performed by a basestation, comprising: receiving, from a user equipment (UE), assistanceinformation that indicates a packet data convergence protocol (PDCP)preference for multiple connectivity communications from a master nodeand one or more secondary nodes; and transmitting, to the UE, acommunication that indicates a routing of a sequence of PDCP packagesacross the master node and one or more active secondary nodes.

Aspect 17: The method of Aspect 16, further comprising: coordinatingscheduling of multiple connectivity communications to the UE with one ormore other base stations based at least in part on the PDCP preference.

Aspect 18: The method of Aspect 17, wherein coordinating scheduling ofmultiple connectivity communications to the UE with the one or moreother base stations comprises coordinating scheduling of delivery of thePDCP sequence to the UE with the one or more other base stations basedat least in part on the at least one of the PDCP sequence gap preferenceor the PDCP arrival time preference.

Aspect 19: The method of any of Aspects 16-18, wherein the base stationis at least one of the master node or a secondary node of the one ormore secondary nodes.

Aspect 20: The method of any of Aspects 16-19, wherein the PDCPpreference includes a preference for a PDCP sequence gap for the PDCPpackages transmitted by the master node and the one or more activesecondary nodes.

Aspect 21: The method of Aspect 20, wherein the preference for the PDCPsequence gap includes at least one of a minimum PDCP sequence gap or amaximum PDCP sequence gap.

Aspect 22: The method of any of Aspects 20-21, wherein the preferencefor the PDCP sequence gap is based at least in part on a buffer size ofthe UE or latency parameters for traffic associated with the UE.

Aspect 23: The method of any of Aspects 16-22, wherein the PDCPpreference includes a PDCP arrival time preference for the PDCP packagestransmitted by the master node and the one or more active secondarynodes.

Aspect 24: The method of Aspect 23, wherein the PDCP arrival timepreference indicates a preferred maximum time difference betweenarrivals of consecutive PDCP packages of the sequence of PDCP packagesfrom the master node and the one or more active secondary nodes.

Aspect 25: The method of any of Aspects 23-24, wherein the PDCP arrivaltime preference is based at least in part on a buffer size of the UE orlatency parameters for traffic associated with the UE.

Aspect 26: The method of any of Aspects 16-25, wherein the PDCPpreference includes at least one of a PDCP splitting preference thatspecifies a preference for the master node or one of the activesecondary nodes to perform splitting of the sequence of PDCP packages,or a PDCP routing preference that specifies a preference for the masternode or one of the active secondary nodes to perform routing of thesequence of PDCP packages.

Aspect 27: The method of any of Aspects 16-26, wherein the assistanceinformation is included in at least one of a radio resource controlcommunication, a medium access control (MAC) control element, or achannel status information report.

Aspect 28: The method of any of Aspects 16-27, wherein the communicationis at least one of a radio resource control communication, physicaldownlink control channel downlink control information, or a mediumaccess control (MAC) control element.

Aspect 29: The method of any of Aspects 16-28, wherein the assistanceinformation is included in at least one of a call setup request, a callresume request, or a measurement report for a call handover.

Aspect 30: The method of any of Aspects 16-29, wherein the assistanceinformation is received by the base station during an ongoing call.

Aspect 31: The method of any of Aspects 30, wherein the PDCP preferenceincludes at least one of a PDCP sequence gap preference or a PDCParrival time preference, and the communication includes an indicationrelating to scheduling delivery of the sequence of PDCP packages basedat least in part on the at least one of the PDCP sequence gap preferenceor the PDCP arrival time preference.

Aspect 32: The method of any of Aspects 30-31, wherein the PDCPpreference includes at least one of a PDCP sequence gap preference or aPDCP arrival time preference, and the communication includes at leastone PDCP package of the sequence of PDCP packages scheduled based atleast in part on the at least one of the PDCP sequence gap preference orthe PDCP arrival time preference.

Aspect 33: A method of wireless communication performed by a userequipment (UE), comprising: transmitting, to a base station, assistanceinformation that indicates a secondary node configuration preference formultiple connectivity communications from a master node and one or moresecondary nodes; and receiving, from the base station, a communicationthat indicates a secondary node for the UE.

Aspect 34: The method of Aspect 33, wherein the base station is at leastone of the master node or a secondary node of the one or more secondarynodes.

Aspect 35: The method of any of Aspects 33-34, wherein the secondarynode configuration preference includes at least one of a preferrednumber of activated secondary nodes or a preferred number of deactivatedsecondary nodes.

Aspect 36: The method of any of Aspects 33-36, wherein the secondarynode configuration preference includes at least one of a preferred setof activated secondary nodes of the one or more secondary nodes or apreferred set of deactivated secondary nodes of the one or moresecondary nodes.

Aspect 37: The method of any of Aspects 33-36, wherein the secondarynode configuration preference includes at least one of a preferred setof non-dormant activated secondary nodes of the one or more secondarynodes or a preferred set of dormant activated secondary nodes of the oneor more secondary nodes.

Aspect 38: The method of any of Aspects 33-37, wherein the secondarynode configuration preference includes a UE feedback preference for theone or more secondary nodes.

Aspect 39: The method of Aspect 38, wherein the UE feedback preferenceindicates a preference for layer 1 feedback or layer 2 feedback from theUE for communications received from the one or more secondary nodes.

Aspect 40: The method of any of Aspects 38-39, wherein the UE feedbackpreference indicates a preference to send feedback for communicationsreceived from the one or more secondary nodes to the one or moresecondary nodes or a preference to send feedback for communicationsreceived from the one or more secondary nodes to the master node.

Aspect 41: The method of any of Aspects 33-40, wherein the assistanceinformation is included in at least one of a radio resource controlcommunication, a medium access control (MAC) control element, or achannel status information report.

Aspect 42: The method of any of Aspects 33-41, wherein the communicationis at least one of a radio resource control communication, physicaldownlink control channel downlink control information, or a mediumaccess control (MAC) control element.

Aspect 43: The method of any of Aspects 33-42, wherein the assistanceinformation is included in at least one of a call setup request, a callresume request, or a measurement report for a call handover.

Aspect 44: The method of Aspect 43, wherein the secondary nodeconfiguration specifies at least one of a configuration of the one ormore secondary nodes for multiple connectivity communications or are-configuration of the one or more secondary nodes for multipleconnectivity communications.

Aspect 45: The method of any of Aspects 33-44, wherein the assistanceinformation is transmitted to the base station during an ongoing call.

Aspect 46: The method of Aspect 45, wherein the communication includesan indication of a state change for at least one secondary node of theone or more secondary nodes.

Aspect 47: The method of any of Aspects 45-46, wherein the secondarynode configuration preference includes a UE feedback preference, and thecommunication includes an indication of a change to a feedback mode forthe UE based at least in part on the UE feedback preference.

Aspect 48: A method of wireless communication performed by a basestation, comprising: receiving, from a user equipment (UE), assistanceinformation that indicates a secondary node configuration preference formultiple connectivity communications from a master node and one or moresecondary nodes; and transmitting, to the UE, a communication thatindicates a secondary node configuration for the UE.

Aspect 49: The method of Aspect 48, further comprising: coordinatingscheduling of multiple connectivity communications to the UE with one ormore other base stations based at least in part on the secondary nodeconfiguration preference.

Aspect 50: The method of any of Aspects 48-49, wherein the base stationis at least one of the master node or a secondary node of the one ormore secondary nodes.

Aspect 51: The method of any of Aspects 48-50, wherein the secondarynode configuration preference includes at least one of a preferrednumber of activated secondary nodes or a preferred number of deactivatedsecondary nodes.

Aspect 52: The method of any of Aspects 48-51, wherein the secondarynode configuration preference includes at least one of a preferred setof activated secondary nodes of the one or more secondary nodes or apreferred set of deactivated secondary nodes of the one or moresecondary nodes.

Aspect 53: The method of any of Aspects 48-52, wherein the secondarynode configuration preference includes at least one of a preferred setof non-dormant activated secondary nodes of the one or more secondarynodes or a preferred set of dormant activated secondary nodes of the oneor more secondary nodes.

Aspect 54: The method of any of Aspects 48-53, wherein the secondarynode configuration preference includes a UE feedback preference for theone or more secondary nodes.

Aspect 55: The method of Aspect 54, wherein the UE feedback preferenceindicates a preference for layer 1 feedback or layer 2 feedback from theUE for communications received from the one or more secondary nodes.

Aspect 56: The method of any of Aspects 54-55, wherein the UE feedbackpreference indicates a preference to send feedback for communicationsreceived from the one or more secondary nodes to the one or moresecondary nodes or a preference to send feedback for communicationsreceived from the one or more secondary nodes to the master node.

Aspect 57: The method of any of Aspects 48-56, wherein the assistanceinformation is included in at least one of a radio resource controlcommunication, a medium access control (MAC) control element, or achannel status information report.

Aspect 58: The method of any of Aspects 48-57, wherein the communicationis at least one of a radio resource control communication, physicaldownlink control channel downlink control information, or a mediumaccess control (MAC) control element.

Aspect 59: The method of any of Aspects 48-58, wherein the assistanceinformation is included in at least one of a call setup request, a callresume request, or a measurement report for a call handover.

Aspect 60: The method of Aspect 59, wherein the communication includesthe secondary node configuration, and the secondary node configurationspecifies at least one of a configuration of the one or more secondarynodes for multiple connectivity communications or a re-configuration ofthe one or more secondary nodes for multiple connectivitycommunications.

Aspect 61: The method of any of Aspects 48-60, wherein the assistanceinformation is received by the base station during an ongoing call.

Aspect 62: The method of Aspect 61, wherein the communication includesan indication of a state change for at least one secondary node of theone or more secondary nodes.

Aspect 63: The method of any of Aspects 61-62, wherein the secondarynode configuration preference includes a UE feedback preference, and thecommunication includes an indication of a change to a feedback mode forthe UE based at least in part on the UE feedback preference.

Aspect 64: A method of wireless communication performed by a userequipment (UE), comprising: transmitting, to a base station, assistanceinformation that indicates at least one of a packet data convergenceprotocol (PDCP) preference or a secondary node configuration preferencefor multiple connectivity communications from a master node and one ormore secondary nodes; and receiving, from the base station, acommunication that indicates at least one of a secondary nodeconfiguration or a routing of a sequence of PDCP packages across themaster node and one or more active secondary nodes.

Aspect 65: The method of Aspect 64, wherein the base station is at leastone of the master node or a secondary node of the one or more secondarynodes.

Aspect 66: The method of any of Aspects 64-65, wherein the assistanceinformation includes the PDCP preference.

Aspect 67: The method of Aspect 66, wherein the PDCP preference includesa preference for a PDCP sequence gap for the PDCP packages transmittedby the master node and the one or more active secondary nodes.

Aspect 68: The method of Aspect 67, wherein the preference for the PDCPsequence gap includes at least one of a minimum PDCP sequence gap or amaximum PDCP sequence gap.

Aspect 69: The method of any of Aspects 67-68, wherein the preferencefor the PDCP sequence gap is based at least in part on a buffer size ofthe UE or latency parameters for traffic associated with the UE.

Aspect 70: The method of any of Aspects 66-69, wherein the PDCPpreference includes a PDCP arrival time preference for the PDCP packagestransmitted by the master node and the one or more active secondarynodes.

Aspect 71: The method of Aspect 70, wherein the PDCP arrival timepreference indicates a preferred maximum time difference betweenarrivals of consecutive PDCP packages of the sequence of PDCP packagesfrom the master node and the one or more active secondary nodes.

Aspect 72: The method of any of Aspects 70-71, wherein the PDCP arrivaltime preference is based at least in part on a buffer size of the UE orlatency parameters for traffic associated with the UE.

Aspect 73: The method of any of Aspects 66-72, wherein the PDCPpreference includes at least one of a PDCP splitting preference thatspecifies a preference for the master node or one of the activesecondary nodes to perform splitting of the sequence of PDCP packages,or a PDCP routing preference that specifies a preference for the masternode or one of the active secondary nodes to perform routing of thesequence of PDCP packages.

Aspect 74: The method of any of Aspects 64-73, wherein the assistanceinformation includes the secondary node configuration preference.

Aspect 75: The method of Aspect 74, wherein the secondary nodeconfiguration preference includes at least one of a preferred number ofactivated secondary nodes or a preferred number of deactivated secondarynodes.

Aspect 76: The method of any of Aspects 74-75, wherein the secondarynode configuration preference includes at least one of a preferred setof activated secondary nodes of the one or more secondary nodes or apreferred set of deactivated secondary nodes of the one or moresecondary nodes.

Aspect 77: The method of any of Aspects 74-76, wherein the secondarynode configuration preference includes at least one of a preferred setof non-dormant activated secondary nodes of the one or more secondarynodes or a preferred set of dormant activated secondary nodes of the oneor more secondary nodes.

Aspect 78: The method of any of Aspects 74-77, wherein the secondarynode configuration preference includes a UE feedback preference for theone or more secondary nodes.

Aspect 79: The method of Aspect 78, wherein the UE feedback preferenceindicates a preference for layer 1 feedback or layer 2 feedback from theUE for communications received from the one or more secondary nodes.

Aspect 80: The method of any of Aspects 78-79, wherein the UE feedbackpreference indicates a preference to send feedback for communicationsreceived from the one or more secondary nodes to the one or moresecondary nodes or a preference to send feedback for communicationsreceived from the one or more secondary nodes to the master node.

Aspect 81: The method of any of Aspects 64-80, wherein the assistanceinformation is included in at least one of a radio resource controlcommunication, a medium access control (MAC) control element, or achannel status information report.

Aspect 82: The method of any of Aspects 64-81, wherein the communicationis at least one of a radio resource control communication, physicaldownlink control channel downlink control information, or a mediumaccess control (MAC) control element.

Aspect 83: The method of any of Aspects 64-82, wherein the assistanceinformation is included in at least one of a call setup request, a callresume request, or a measurement report for a call handover.

Aspect 84: The method of Aspect 83, wherein the communication includesthe secondary node configuration, and the secondary node configurationspecifies at least one of a configuration of the one or more secondarynodes for multiple connectivity communications or a re-configuration ofthe one or more secondary nodes for multiple connectivitycommunications.

Aspect 85: The method of any of Aspects 64-84, wherein the assistanceinformation is transmitted to the base station during an ongoing call.

Aspect 86: The method of Aspect 85, wherein the communication includesan indication of a state change for at least one secondary node of theone or more secondary nodes.

Aspect 87: The method of any of Aspects 85-86, wherein the PDCPpreference includes at least one of a PDCP sequence gap preference or aPDCP arrival time preference, and the communication includes anindication relating to scheduling delivery of the sequence of PDCPpackages based at least in part on the at least one of the PDCP sequencegap preference or the PDCP arrival time preference.

Aspect 88: The method of any of Aspects 85-87, wherein the PDCPpreference includes at least one of a PDCP sequence gap preference or aPDCP arrival time preference, and the communication includes at leastone PDCP package of a sequence of PDCP packages scheduled based at leastin part on the at least one of the PDCP sequence gap preference or thePDCP arrival time preference.

Aspect 89: The method of any of Aspects 85-88, wherein the secondarynode configuration preference includes a UE feedback preference, and thecommunication includes an indication of a change to a feedback mode forthe UE based at least in part on the UE feedback preference.

Aspect 90: A method of wireless communication performed by a basestation, comprising: receiving, from a user equipment (UE), assistanceinformation that indicates at least one of a packet data convergenceprotocol (PDCP) preference or a secondary node configuration preferencefor multiple connectivity communications from a master node and one ormore secondary nodes; and transmitting, to the UE, a communication thatindicates at least one of a secondary node configuration or a routing ofa sequence of PDCP packages across the master node and one or moreactive secondary nodes.

Aspect 91: The method of Aspect 90, further comprising: coordinatingscheduling of multiple connectivity communications to the UE with one ormore other base stations based at least in part on the at least one ofthe PDCP preference or the secondary node configuration preference.

Aspect 92: The method of Aspect 91, wherein the PDCP preference includesat least one of a PDCP sequence gap preference or a PDCP arrival timepreference, and coordinating scheduling of multiple connectivitycommunications to the UE with the one or more other base stationscomprises coordinating scheduling of delivery of the PDCP sequence tothe UE with the one or more other base stations based at least in parton the at least one of the PDCP sequence gap preference or the PDCParrival time preference.

Aspect 93: The method of any of Aspects 90-92, wherein the base stationis at least one of the master node or a secondary node of the one ormore secondary nodes.

Aspect 94: The method of any of Aspects 90-93, wherein the assistanceinformation includes the PDCP preference.

Aspect 95: The method of Aspect 94, wherein the PDCP preference includesa preference for a PDCP sequence gap for the PDCP packages transmittedby the master node and the one or more active secondary nodes.

Aspect 96: The method of Aspect 95, wherein the preference for the PDCPsequence gap includes at least one of a minimum PDCP sequence gap or amaximum PDCP sequence gap.

Aspect 97: The method of any of Aspects 95-96, wherein the preferencefor the PDCP sequence gap is based at least in part on a buffer size ofthe UE or latency parameters for traffic associated with the UE.

Aspect 98: The method of any of Aspects 94-97, wherein the PDCPpreference includes a PDCP arrival time preference for the PDCP packagestransmitted by the master node and the one or more active secondarynodes.

Aspect 99: The method of Aspect 98, wherein the PDCP arrival timepreference indicates a preferred maximum time difference betweenarrivals of consecutive PDCP packages of the sequence of PDCP packagesfrom the master node and the one or more active secondary nodes.

Aspect 100: The method of any of Aspects 98-99, wherein the PDCP arrivaltime preference is based at least in part on a buffer size of the UE orlatency parameters for traffic associated with the UE.

Aspect 101: The method of any of Aspects 94-100, wherein the PDCPpreference includes at least one of a PDCP splitting preference thatspecifies a preference for the master node or one of the activesecondary nodes to perform splitting of the sequence of PDCP packages,or a PDCP routing preference that specifies a preference for the masternode or one of the active secondary nodes to perform routing of thesequence of PDCP packages.

Aspect 102: The method of any of Aspects 90-101, wherein the assistanceinformation includes the secondary node configuration preference.

Aspect 103: The method of Aspect 102, wherein the secondary nodeconfiguration preference includes at least one of a preferred number ofactivated secondary nodes or a preferred number of deactivated secondarynodes.

Aspect 104: The method of any of Aspects 102-103, wherein the secondarynode configuration preference includes at least one of a preferred setof activated secondary nodes of the one or more secondary nodes or apreferred set of deactivated secondary nodes of the one or moresecondary nodes.

Aspect 105: The method of any of Aspects 102-104, wherein the secondarynode configuration preference includes at least one of a preferred setof non-dormant activated secondary nodes of the one or more secondarynodes or a preferred set of dormant activated secondary nodes of the oneor more secondary nodes.

Aspect 106: The method of any of Aspects 102-105, wherein the secondarynode configuration preference includes a UE feedback preference for theone or more secondary nodes.

Aspect 107: The method of Aspect 106, wherein the UE feedback preferenceindicates a preference for layer 1 feedback or layer 2 feedback from theUE for communications received from the one or more secondary nodes.

Aspect 108: The method of any of Aspects 106-107, wherein the UEfeedback preference indicates a preference to send feedback forcommunications received from the one or more secondary nodes to the oneor more secondary nodes or a preference to send feedback forcommunications received from the one or more secondary nodes to themaster node.

Aspect 109: The method of any of Aspects 90-108, wherein the assistanceinformation is included in at least one of a radio resource controlcommunication, a medium access control (MAC) control element, or achannel status information report.

Aspect 110: The method of any of Aspects 90-109, wherein thecommunication is at least one of a radio resource control communication,physical downlink control channel downlink control information, or amedium access control (MAC) control element.

Aspect 111: The method of any of Aspects 90-110, wherein the assistanceinformation is included in at least one of a call setup request, a callresume request, or a measurement report for a call handover.

Aspect 112: The method of Aspect 111, wherein the communication includesthe secondary node configuration, and the secondary node configurationspecifies at least one of a configuration of the one or more secondarynodes for multiple connectivity communications or a re-configuration ofthe one or more secondary nodes for multiple connectivitycommunications.

Aspect 113: The method of any of Aspects 90-112, wherein the assistanceinformation is received by the base station during an ongoing call.

Aspect 114: The method of Aspect 113, wherein the communication includesan indication of a state change for at least one secondary node of theone or more secondary nodes.

Aspect 115: The method of any of Aspects 113-114, wherein the PDCPpreference includes at least one of a PDCP sequence gap preference or aPDCP arrival time preference, and the communication includes anindication relating to scheduling delivery of the sequence of PDCPpackages based at least in part on the at least one of the PDCP sequencegap preference or the PDCP arrival time preference.

Aspect 116: The method of any of Aspects 113-115, wherein the PDCPpreference includes at least one of a PDCP sequence gap preference or aPDCP arrival time preference, and the communication includes at leastone PDCP package of the sequence of PDCP packages scheduled based atleast in part on the at least one of the PDCP sequence gap preference orthe PDCP arrival time preference.

Aspect 117: The method of any of Aspects 113-116, wherein the secondarynode configuration preference includes a UE feedback preference, and thecommunication includes an indication of a change to a feedback mode forthe UE based at least in part on the UE feedback preference.

Aspect 118: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects1-15.

Aspect 119: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects16-32.

Aspect 120: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects33-47.

Aspect 121: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects48-63.

Aspect 122: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects64-89.

Aspect 123: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects90-117.

Aspect 124: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 1-117.

Aspect 125: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 16-32.

Aspect 126: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 33-47.

Aspect 127: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 48-63.

Aspect 128: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 64-89.

Aspect 129: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 90-117.

Aspect 130: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 1-15.

Aspect 131: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 16-32.

Aspect 132: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 33-47.

Aspect 133: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 48-63.

Aspect 134: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 64-89.

Aspect 135: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 90-117.

Aspect 136: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 1-15.

Aspect 137: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 16-32.

Aspect 138: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 33-47.

Aspect 139: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 48-63.

Aspect 140: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 64-89.

Aspect 141: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 90-117.

Aspect 142: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 1-15.

Aspect 143: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 16-32.

Aspect 144: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 33-47.

Aspect 145: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 48-63.

Aspect 144: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 64-89.

Aspect 145: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 90-117.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware and/or a combination of hardware and software. “Software”shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,and/or functions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a “processor” is implemented in hardwareand/or a combination of hardware and software. It will be apparent thatsystems and/or methods described herein may be implemented in differentforms of hardware and/or a combination of hardware and software. Theactual specialized control hardware or software code used to implementthese systems and/or methods is not limiting of the aspects. Thus, theoperation and behavior of the systems and/or methods are describedherein without reference to specific software code, since those skilledin the art will understand that software and hardware can be designed toimplement the systems and/or methods based, at least in part, on thedescription herein.

As used herein, “satisfying a threshold” may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. Many of thesefeatures may be combined in ways not specifically recited in the claimsand/or disclosed in the specification. The disclosure of various aspectsincludes each dependent claim in combination with every other claim inthe claim set. As used herein, a phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination withmultiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b,a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b,and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items andmay be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” or the like are intendedto be open-ended terms that do not limit an element that they modify(e.g., an element “having” A may also have B). Further, the phrase“based on” is intended to mean “based, at least in part, on” unlessexplicitly stated otherwise. Also, as used herein, the term “or” isintended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (e.g.,if used in combination with “either” or “only one of”).

What is claimed is:
 1. A method of wireless communication performed by auser equipment (UE), comprising: transmitting, to a base station,assistance information that indicates a packet data convergence protocol(PDCP) preference for multiple connectivity communications from a masternode and one or more secondary nodes; and receiving, from the basestation, a communication that indicates a routing of a sequence of PDCPpackages across the master node and one or more active secondary nodes.2. The method of claim 1, wherein the PDCP preference includes apreference for a PDCP sequence gap for the PDCP packages transmitted bythe master node and the one or more active secondary nodes, and whereinthe preference for the PDCP sequence gap includes at least one of aminimum PDCP sequence gap or a maximum PDCP sequence gap.
 3. The methodof claim 1, wherein the PDCP preference includes a PDCP arrival timepreference for the PDCP packages transmitted by the master node and theone or more active secondary nodes, and wherein the PDCP arrival timepreference indicates a preferred maximum time difference betweenarrivals of consecutive PDCP packages of the sequence of PDCP packagesfrom the master node and the one or more active secondary nodes.
 4. Themethod of claim 1, wherein the PDCP preference includes at least one ofa PDCP splitting preference that specifies a preference for the masternode or one of the active secondary nodes to perform splitting of thesequence of PDCP packages, or a PDCP routing preference that specifies apreference for the master node or one of the active secondary nodes toperform routing of the sequence of PDCP packages.
 5. The method of claim1, wherein the assistance information is transmitted to the base stationduring an ongoing call or the assistance information is included in atleast one of a call setup request, a call resume request, or ameasurement report for a call handover.
 6. A method of wirelesscommunication performed by a user equipment (UE), comprising:transmitting, to a base station, assistance information that indicates asecondary node configuration preference for multiple connectivitycommunications from a master node and one or more secondary nodes; andreceiving, from the base station, a communication that indicates asecondary node configuration for the UE.
 7. The method of claim 6,wherein the secondary node configuration preference includes at leastone of a preferred number of activated secondary nodes or a preferrednumber of deactivated secondary nodes.
 8. The method of claim 6, whereinthe secondary node configuration preference includes at least one of apreferred set of activated secondary nodes of the one or more secondarynodes or a preferred set of deactivated secondary nodes of the one ormore secondary nodes.
 9. The method of claim 6, wherein the secondarynode configuration preference includes at least one of a preferred setof non-dormant activated secondary nodes of the one or more secondarynodes or a preferred set of dormant activated secondary nodes of the oneor more secondary nodes.
 10. The method of claim 6, wherein thesecondary node configuration preference includes a UE feedbackpreference for the one or more secondary nodes, and wherein the UEfeedback preference indicates at least one of: a preference for layer 1feedback or layer 2 feedback from the UE for communications receivedfrom the one or more secondary nodes, or a preference to send feedbackfor communications received from the one or more secondary nodes to theone or more secondary nodes or to the master node.
 11. The method ofclaim 6, wherein the assistance information is transmitted to the basestation during an ongoing call or the assistance information is includedin at least one of a call setup request, a call resume request, or ameasurement report for a call handover.
 12. A user equipment (UE) forwireless communication, comprising: a memory; and one or more processorscoupled to the memory, the memory and the one or more processorsconfigured to: transmit, to a base station, assistance information thatindicates a packet data convergence protocol (PDCP) preference formultiple connectivity communications from a master node and one or moresecondary nodes; and receive, from the base station, a communicationthat indicates a routing of a sequence of PDCP packages across themaster node and one or more active secondary nodes.
 13. The UE of claim12, wherein the PDCP preference includes a preference for a PDCPsequence gap for the PDCP packages transmitted by the master node andthe one or more active secondary nodes, and wherein the preference forthe PDCP sequence gap includes at least one of a minimum PDCP sequencegap or a maximum PDCP sequence gap.
 14. The UE of claim 12, wherein thePDCP preference includes a PDCP arrival time preference for the PDCPpackages transmitted by the master node and the one or more activesecondary nodes, and wherein the PDCP arrival time preference indicatesa preferred maximum time difference between arrivals of consecutive PDCPpackages of the sequence of PDCP packages from the master node and theone or more active secondary nodes.
 15. The UE of claim 12, wherein thePDCP preference includes at least one of PDCP sequence gap preference ora PDCP arrival time preference, and wherein the at least one of the PDCPsequence gap preference or the PDCP arrival time preference is based atleast in part on a buffer size of the UE or latency parameters fortraffic associated with the UE.
 16. The UE of claim 12, wherein the PDCPpreference includes at least one of a PDCP splitting preference thatspecifies a preference for the master node or one of the activesecondary nodes to perform splitting of the sequence of PDCP packages,or a PDCP routing preference that specifies a preference for the masternode or one of the active secondary nodes to perform routing of thesequence of PDCP packages.
 17. The UE of claim 12, wherein theassistance information is included in at least one of a call setuprequest, a call resume request, or a measurement report for a callhandover.
 18. The UE of claim 12, wherein the one or more processor, totransmit the assistance information, are configured to: transmit theassistance information to the base station during an ongoing call. 19.The UE of claim 18, wherein the PDCP preference includes at least one ofa PDCP sequence gap preference or a PDCP arrival time preference, andthe communication includes an indication relating to scheduling deliveryof the sequence of PDCP packages based at least in part on the at leastone of the PDCP sequence gap preference or the PDCP arrival timepreference.
 20. The UE of claim 18, wherein the PDCP preference includesat least one of a PDCP sequence gap preference or a PDCP arrival timepreference, and the communication includes at least one PDCP package ofa sequence of PDCP packages scheduled based at least in part on the atleast one of the PDCP sequence gap preference or the PDCP arrival timepreference.
 21. A user equipment (UE) for wireless communication,comprising: a memory; and one or more processors coupled to the memory,the memory and the one or more processors configured to: transmit, to abase station, assistance information that indicates a secondary nodeconfiguration preference for multiple connectivity communications from amaster node and one or more secondary nodes; and receive, from the basestation, a communication that indicates a secondary node configurationfor the UE.
 22. The UE of claim 21, wherein the secondary nodeconfiguration preference includes at least one of a preferred number ofactivated secondary nodes or a preferred number of deactivated secondarynodes.
 23. The UE of claim 21, wherein the secondary node configurationpreference includes at least one of a preferred set of activatedsecondary nodes of the one or more secondary nodes or a preferred set ofdeactivated secondary nodes of the one or more secondary nodes.
 24. TheUE of claim 21, wherein the secondary node configuration preferenceincludes at least one of a preferred set of non-dormant activatedsecondary nodes of the one or more secondary nodes or a preferred set ofdormant activated secondary nodes of the one or more secondary nodes.25. The UE of claim 21, wherein the secondary node configurationpreference includes a UE feedback preference for the one or moresecondary nodes, and wherein the UE feedback preference indicates atleast one of: a preference for layer 1 feedback or layer 2 feedback fromthe UE for communications received from the one or more secondary nodes,or a preference to send feedback for communications received from theone or more secondary nodes to the one or more secondary nodes or to themaster node.
 26. The UE of claim 21, wherein the assistance informationis included in at least one of a call setup request, a call resumerequest, or a measurement report for a call handover.
 27. The UE ofclaim 26, wherein the secondary node configuration specifies at leastone of a configuration of the one or more secondary nodes for multipleconnectivity communications or a re-configuration of the one or moresecondary nodes for multiple connectivity communications.
 28. The UE ofclaim 21, wherein the one or more processors, to transmit the assistanceinformation, are configured to: transmit the assistance information tothe base station during an ongoing call.
 29. The UE of claim 28, whereinthe communication includes an indication of a state change for at leastone secondary node of the one or more secondary nodes.
 30. The UE ofclaim 28, wherein the secondary node configuration preference includes aUE feedback preference, and the communication includes an indication ofa change to a feedback mode for the UE based at least in part on the UEfeedback preference.